Skip to content

Hostname

mykplan.com

Last fetched

mykplan.com resolves to 170.146.92.153, announced in 170.146.92.0/23 by ADP1 - Automatic Data Processing, Inc. in US. mykplan.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 · mykplan.comRouting diversity2.4/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.3/10canon.whisper.security/host/mykplan.com

Resolution chain

IPv6 resolution

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

Attribution

automatic processing

ORIGIN_AS

WHOIS identity

Registrar
iana:292
Registrant organisation
adp, llc.
Contact emails
hostmaster@adp.com

Subdomains

Subdomain
phr-test1.mykplan.com
phr.mykplan.com
test1.mykplan.com
test2.mykplan.com
test3.mykplan.com
test4.mykplan.com
test5.mykplan.com
testhotfix.mykplan.com
testrc.mykplan.com
www.mykplan.com

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

  • dc01exdnsgm.net.adp.com
  • a1-199.akam.net
  • a14-65.akam.net
  • a18-66.akam.net
  • a28-64.akam.net
  • a5-66.akam.net
  • a9-67.akam.net
  • dns1.p01.nsone.net
  • dns2.p01.nsone.net
  • dns3.p01.nsone.net
  • dns4.p01.nsone.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

Threat-feed evidence

History

Related pages

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