Hostname
froschvacations.com
Last fetched
froschvacations.com resolves to 52.249.56.137, announced in 52.224.0.0/11 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. froschvacations.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
- 52.249.56.137
52.224.0.0/11 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · San Antonio, US
IPv6 resolution
No AAAA record for froschvacations.com is recorded in WhisperGraph.
Attribution
Github
saas · ORIGIN_AS
WHOIS identity
- Registrar
- iana:292
- Registrant organisation
- domain administrator
- Contact emails
- ax48b2p55jz@networksolutionsprivateregistration.com, b45ma7hm7dz@networksolutionsprivateregistration.com, domainregistration@jpmchase.com, fa9g72936rs@networksolutionsprivateregistration.com, hr4fx8xb8sz@networksolutionsprivateregistration.com, qa94r5jm87a@networksolutionsprivateregistration.com, qs6rs3953rc@networksolutionsprivateregistration.com, qu6mg6p539m@networksolutionsprivateregistration.com, qx3z57ju237@networksolutionsprivateregistration.com, vm3qk98h2bt@networksolutionsprivateregistration.com, w35ae8yg4n4@networksolutionsprivateregistration.com, wk3d37aj82g@networksolutionsprivateregistration.com
Subdomains
Showing 12 of 20. View all subdomains →
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
Mail and authentication
Nameservers
- ns0037.secondary.cloudflare.com
- ns0246.secondary.cloudflare.com
- ns05.jpmorganchase.com
- ns06.jpmorganchase.com
- ns1.jpmorganchase.com
- ns2.jpmorganchase.com
MX records
- froschvacations-com.mail.protection.outlook.com
SPF policy
- ip: 198.58.72.11/32
- ip: 63.131.146.17/32
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from froschvacations.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: "froschvacations.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.