Public dataConnector
Infosec
Read WHOIS, DNS, SPF/DMARC, subdomains and TLS configuration for any domain, passively and with no API key, from Claude or ChatGPT through Tulina's MCP server.
What it can do
2 read/1 send
- 01Read
Read WHOIS/RDAP and DNS records for a domain
- 02Send
Check email posture (SPF/DMARC) and enumerate subdomains via Certificate Transparency
- 03Read
Read TLS configuration and security headers
Open data: no credential to issue, hold or revoke. Passive reconnaissance only — this reads what is already public, and touches nothing.
How do you connect Infosec to Claude and ChatGPT?
Through Tulina's MCP server, reading only what's already public — no API key required. Pull WHOIS/RDAP and DNS records for a domain, check its email posture (SPF/DMARC) and enumerate subdomains via Certificate Transparency, or read its TLS configuration and security headers, from the same chat as Claude or ChatGPT.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Infosec once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Infosec at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Infosec returns something usable instead of something generic.
Processes that run on Infosec
None published yet.