Skip to content
Install MCP

Hostname

mcnet.ad.jp

Last fetched

mcnet.ad.jp resolves to 210.172.32.50, announced in 210.172.32.0/19 by MCNET - NTT SmartConnect Corporation in JP. mcnet.ad.jp 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 · mcnet.ad.jpRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/mcnet.ad.jp

Resolution chain

IPv6 resolution

No AAAA record for mcnet.ad.jp is recorded in WhisperGraph.

Attribution

ntt smartconnect

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mcnet.ad.jp. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
admin.mcnet.ad.jp
admin3.mcnet.ad.jp
agari.mcnet.ad.jp
col1.mcnet.ad.jp
col2.mcnet.ad.jp
customer.mcnet.ad.jp
dhcp-150.mcnet.ad.jp
dhcp-153.mcnet.ad.jp
dhcp-154.mcnet.ad.jp
fns01.mcnet.ad.jp
fns02.mcnet.ad.jp
fns03.mcnet.ad.jp

Showing 12 of 42. View all subdomains →

Mail and authentication

Nameservers

  • ns10.nttsmc.com
  • ns.mcnet.ad.jp
  • ns2.mcnet.ad.jp
  • 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

MX records

  • agari.mcnet.ad.jp
  • gari.mcnet.ad.jp

SPF policy

  • ip: 219.96.78.0/28
  • ip: 219.96.79.0/29
  • ip: 210.172.35.32/28
  • ip: 219.96.78.80/28
  • include: dc.nttsmc.com.spf.hosting-pf.net

Threat-feed evidence

History

Related pages

Pivot from mcnet.ad.jp 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: "mcnet.ad.jp"})-[: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.