Skip to content

Hostname

planmyservice.com

Last fetched

planmyservice.com resolves to 158.255.230.138, announced in 158.255.230.0/24 by NODE4-AS - Node4 Limited in GB. planmyservice.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 · planmyservice.comRouting diversity1.5/10Peering density5.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/planmyservice.com

Resolution chain

IPv6 resolution

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

Attribution

node4

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
monitoring@edynamix.co.uk

Subdomains

Mail and authentication

Nameservers

  • ns03.domaincontrol.com
  • ns04.domaincontrol.com

MX records

  • mx.planmyservice.com
  • mx2.planmyservice.com
  • mx3.planmyservice.com
  • mx4.planmyservice.com
  • mx5.planmyservice.com

SPF policy

  • mx: planmyservice.com
  • ip: 158.255.230.131
  • ip: 158.255.230.135
  • ip: 158.255.230.139
  • ip: 83.166.160.49
  • ip: 93.174.141.36
  • ip: 93.174.141.38

Threat-feed evidence

History

Related pages

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