Hostname
contactive.com
Last fetched
contactive.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. contactive.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
No IPv4 resolution is recorded for contactive.com in WhisperGraph.
IPv6 resolution
No AAAA record for contactive.com is recorded in WhisperGraph.
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of contactive.com owner
- Contact emails
- hostmaster@fuze.com, julio@contactive.com, 3e15f8df-64c8-4943-a440-c20c7cbe452f@identity-protect.org, 45a0b709-e68b-4e13-b5e7-5bf1c7c6bdf8@identity-protect.org, 5088502d-8f11-4243-a0d8-be95e7dce55f@identity-protect.org, 75ce2e11-3807-49d7-9d82-732170a12fcd@identity-protect.org, 77160674-d87b-46d7-a2fe-ed1fa84a66bd@identity-protect.org, 9e333165-80d5-476e-8e08-1308a1556bbd@identity-protect.org, dfe26f04-4633-4e2a-bbd0-923419075309@identity-protect.org, owner-5329611@contactive.com.whoisprivacyservice.org
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns-463.awsdns-57.com
- ns-670.awsdns-19.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1296.awsdns-34.org
- ns-1425.awsdns-50.org
- ns-1876.awsdns-42.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: _spf.google.com
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from contactive.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "contactive.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.