Skip to content

Hostname

custombenefitplans.com

Last fetched

custombenefitplans.com resolves to 66.228.55.71, announced in 66.228.48.0/21 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. custombenefitplans.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 · custombenefitplans.comRouting diversity1.5/10Peering density6.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/custombenefitplans.com

Resolution chain

IPv6 resolution

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

Attribution

akamai

ORIGIN_AS

WHOIS identity

Registrar
iana:299
Registrant organisation
perfect privacy,
Contact emails
bc3yh8p66u4@networksolutionsprivateregistration.com, c89nd7hj2a2@networksolutionsprivateregistration.com, fg97q3k64vp@networksolutionsprivateregistration.com, m32sz9s949p@networksolutionsprivateregistration.com, mk6wh4yx8yh@networksolutionsprivateregistration.com, mw5tx53k2yf@networksolutionsprivateregistration.com, qd6w83635r8@networksolutionsprivateregistration.com, tu92w4tw6bd@networksolutionsprivateregistration.com, us5eh8cq2sr@networksolutionsprivateregistration.com, uz4x67zh378@networksolutionsprivateregistration.com, w68w74gr8u5@networksolutionsprivateregistration.com, wx6vx5v327g@networksolutionsprivateregistration.com, xv2h82a76g2@networksolutionsprivateregistration.com

Subdomains

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

  • udns1.cscdns.net
  • udns2.cscdns.uk

MX records

  • custombenefitplans-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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