Hostname
xact.com
Last fetched
xact.com resolves to 192.133.11.1, announced in 192.133.11.0/24 by CLOUDFLARESPECTRUM - Cloudflare London, LLC in US. xact.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
- 192.133.11.1
192.133.11.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Burlington, US
IPv6 resolution
No AAAA record for xact.com is recorded in WhisperGraph.
Attribution
cloudflare london
ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- inc. synergistic software systems
- Contact emails
- notificationdomainadmin@sharperlending.com, 1bf0ccb109c348a99015d1be13ca0efa.protect@whoisguard.com, spencerm@xact.com, 1b6a8f8b-a653-4828-b58c-c5db36d72ac8@identity-protect.org, 26ecdf3d-d169-4849-8000-bfecbd7f814b@identity-protect.org, 7ee36827-f4fd-4dfa-9e3c-92264f4d0350@identity-protect.org, c2866779-9ef8-419a-aaf6-25e5a1492306@identity-protect.org, cedfcc68-4650-457d-85a6-ab3d57e78ead@identity-protect.org, dd712de9-5844-48d4-9a1d-96c8769f4f27@identity-protect.org, fc173c6e-2e70-419e-b5a5-b1b2e9e69bf5@identity-protect.org, owner-3656917@xact.com.whoisprivacyservice.org, owner-3729484@xact.com.whoisprivacyservice.org, owner-7622672@xact.com.whoisprivacyservice.org, owner-7695239@xact.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.
Sample inbound links
Mail and authentication
Nameservers
- ns-467.awsdns-58.com
- ns-864.awsdns-44.net
- ns-1432.awsdns-51.org
- ns-1700.awsdns-20.co.uk
MX records
- mxa-00373601.gslb.pphosted.com
- mxb-00373601.gslb.pphosted.com
SPF policy
- include: spf.protection.outlook.com
- include: spf-00373601.pphosted.com
- include: _spf.salesforce.com
Threat-feed evidence
History
Related pages
Pivot from xact.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: "xact.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.