Skip to content

Hostname

nailnes.com

Last fetched

nailnes.com resolves to 133.125.49.135, announced in 133.125.0.0/16 by SAKURA-A - SAKURA Internet Inc. in JP. nailnes.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · nailnes.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/nailnes.com

Resolution chain

IPv6 resolution

No AAAA record for nailnes.com is recorded in WhisperGraph.

Attribution

sakura

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of nailnes.com owner
Contact emails
domains@nameserver.ne.jp, 25984912-30e1-4ecb-9ca1-9b81c6516f14@identity-protect.org, 5bd3c3ec-5298-4bce-9d00-13d90f392a54@identity-protect.org, 7e344b86-af04-41c9-b544-09c6b4039ea1@identity-protect.org, d56e4e26-e086-4005-bb9f-b6b877b37dc5@identity-protect.org, d8f47718-8c4e-4b9b-b337-612b0c7de060@identity-protect.org, fb3e148b-098a-4b0c-bb98-8c31ab78edd3@identity-protect.org, ff675664-1135-40b7-b8a3-28062852a96a@identity-protect.org

Subdomains

Subdomain
mail.nailnes.com
sys.nailnes.com
www.nailnes.com

Showing 3 of 3 subdomains (3 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-134.awsdns-16.com
  • ns-774.awsdns-32.net
  • ns-1424.awsdns-50.org
  • ns-1777.awsdns-30.co.uk

MX records

  • mail.nailnes.com

SPF policy

  • mx: nailnes.com
  • include: spf.haihaimail.jp
  • a: sv55.sixcore.ne.jp
  • include: spf.sender.xserver.jp
  • ip: 133.125.49.135
  • ip: 202.226.36.56

Threat-feed evidence

History

Related pages

Pivot from nailnes.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: "nailnes.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.