Hostname
bettermentsecurities.com
Last fetched
bettermentsecurities.com resolves to 6 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists iana:625 as the registrar.
Nutrition Label
Resolution chain
bettermentsecurities.com resolves to 6 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 100.50.17.168 | 100.48.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 100.52.136.117 | 100.48.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.195.52.25 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.215.4.23 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.205.202.35 | 52.200.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.242.9.54 | 54.242.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:625
- Organization
- domain protection services,
- Contact emails
Subdomains
1 observed subdomain of bettermentsecurities.com.
| Subdomain |
|---|
| www.bettermentsecurities.com |
Web-graph footprint
Distinct hostnames that link to or from bettermentsecurities.com in the public web crawl.
5 sites link to this hostname.
Threat posture
History
Mail and authentication
MX records
SPF policy
5 SPF mechanisms authorising senders for bettermentsecurities.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | mail.zendesk.com |
| SPF_INCLUDE | spf.mandrillapp.com |
| SPF_INCLUDE | spf.mtasv.net |
| SPF_IP | 208.81.212.0/22 |
Related pages
Pivot deeper into the graph from bettermentsecurities.com.
- IP · 100.50.17.168
- ASN · AS14618AMAZON-AES - Amazon.com, Inc.
- Registrar · iana:625
- Country · US
- Email · bettermentsecurities.com@protecteddomainservices.com
- TLD · .com
- Browse hostnames · be…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "bettermentsecurities.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.