Hostname
neok12.com
Last fetched
neok12.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. neok12.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 neok12.com in WhisperGraph.
IPv6 resolution
No AAAA record for neok12.com is recorded in WhisperGraph.
WHOIS identity
- Registrar
- iana:1861
- Registrant organisation
- contact privacy inc. customer 0126687843
- Contact emails
- pw-0a9bc89c3d7ab0cafd2ae62b3cb8d10c@privacyguardian.org, pw-0ce147e53710cfaa220e641feff9d2aa@privacyguardian.org, pw-25b0640689c41b41148902fd71943154@privacyguardian.org, pw-2821ae20fe9ee64163349f08cd49fa2d@privacyguardian.org, pw-2a0ec334ebaed97ab5f956b69d954d09@privacyguardian.org, pw-41927993fc93921defa203ed71960428@privacyguardian.org, pw-44ba230aff68fcd0d3d80bada2a3625f@privacyguardian.org, pw-481e9e2ee8b1d0ae08e9e583092a0d76@privacyguardian.org, pw-58483aabd82b133aa03405ba576c6fd6@privacyguardian.org, pw-64df7e97a691110eaebc025aa47cb9e2@privacyguardian.org, pw-a7fd5f2a2fed8e53a0ea32e760bc83e2@privacyguardian.org, pw-b0d9b228f8b4947c63da34a06b7627ff@privacyguardian.org, pw-e3c6271a63f0db8eaac7f817fe9c3d75@privacyguardian.org
Subdomains
| Subdomain |
|---|
| test.neok12.com |
| www.neok12.com |
Showing 2 of 2 subdomains (2 per page).
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
- curitiba.ns.porkbun.com
- fortaleza.ns.porkbun.com
- maceio.ns.porkbun.com
- salvador.ns.porkbun.com
MX records
- mx.zoho.in
- mx2.zoho.in
- mx3.zoho.in
SPF policy
- ip: 213.109.149.96/24
- a: neok12.com
- mx: neok12.com
- include: zoho.in
- include: reliablemail.org
Threat-feed evidence
History
Related pages
Pivot from neok12.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: "neok12.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.