Hostname
primatelabs.com
Last fetched
primatelabs.com resolves to 172.105.16.174, announced in 172.105.0.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in CA. primatelabs.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
IPv6 resolution
IPv6 resolution is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
Attribution is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- john poole
- Contact emails
- namecheap@primatelabs.com, 135f98d2b801432884fce7e70e33e3c5.protect@whoisguard.com, 234ee46c5f4a454bbaa7305c1b67d032.protect@withheldforprivacy.com, 241064be6e0f41ae8da06ea2818733e0.protect@withheldforprivacy.com
Subdomains
Subdomains is temporarily unavailable.
The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.
Mail and authentication
Nameservers
- ns-427.awsdns-53.com
- ns-548.awsdns-04.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-1311.awsdns-35.org
- ns-1671.awsdns-16.co.uk
MX records
- primatelabs-com.mail.protection.outlook.com
SPF policy
- include: cmail1.com
- include: _spf.createsend.com
- include: helpscoutemail.com
- include: spf.protection.outlook.com
- a: primatelabs.com
- mx: primatelabs.com
- include: spf.mtasv.net
Threat-feed evidence
History
Related pages
Pivot from primatelabs.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: "primatelabs.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.