Hostname
bridge-palace.com
Last fetched
bridge-palace.com resolves to 3.72.22.208, announced in 3.64.0.0/12 by AMAZON-02 - Amazon.com, Inc. in DE. bridge-palace.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
- 3.72.22.208
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.79.121.221
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.28.80.232
52.28.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.58.230.131
52.58.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 63.180.118.16
63.180.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 63.182.26.179
63.180.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for bridge-palace.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of bridge-palace.com owner
- Contact emails
- support@spiele-palast.de, webmaster@spiele-palast.de, 5fd30f99-70db-4210-a50b-e1c0b4f7fe0f@identity-protect.org, 81b0797a-6244-47aa-91be-8934ad36f6e2@identity-protect.org, d208e55f-c9bc-41a2-80e6-46185824cf4b@identity-protect.org
Mail and authentication
Nameservers
- ns-489.awsdns-61.com
- ns-975.awsdns-57.net
- 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
- ns-1334.awsdns-38.org
- ns-1735.awsdns-24.co.uk
MX records
- mail.spiele-palast.de
SPF policy
- a: bridge-palace.com
- mx: bridge-palace.com
- include: mail.zendesk.com
- ip: 18.158.10.179
- ip: 52.57.32.220
Threat-feed evidence
History
Related pages
Pivot from bridge-palace.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: "bridge-palace.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.