Hostname
planmember.com
Last fetched
planmember.com resolves to 108.139.47.127, announced in 108.139.44.0/22 by AMAZON-02 - Amazon.com, Inc. in US. planmember.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 108.139.47.127
108.139.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.139.47.129
108.139.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.139.47.49
108.139.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.139.47.86
108.139.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 13.35.78.102
- 13.35.78.36
- 13.35.78.68
- 13.35.78.86
IPv6 resolution
No AAAA record for planmember.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
- Contact emails
- planmember.com@domainsbyproxy.com, hsyed@planmember.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
- ns10.digicertdns.com
- ns0.dnsmadeeasy.com
- ns1.dnsmadeeasy.com
- ns2.dnsmadeeasy.com
- ns3.dnsmadeeasy.com
- ns4.dnsmadeeasy.com
- 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
- usb-smtp-inbound-1.mimecast.com
- usb-smtp-inbound-2.mimecast.com
SPF policy
- ip: 67.231.149.155/32
- ip: 52.1.14.157/32
- ip: 107.20.210.250/32
- ip: 208.86.201.45/32
- include: amazonses.com
- include: _u.planmember.com._spf.dmarclc.com
- include: usb._netblocks.mimecast.com
- include: spf.protection.outlook.com
- ip: 52.32.0.139
Threat-feed evidence
History
Related pages
Pivot from planmember.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: "planmember.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.