Hostname
plaqueomatic.be
Last fetched
plaqueomatic.be resolves to 18.158.202.238, announced in 18.156.0.0/14 by AMAZON-02 - Amazon.com, Inc. in DE. plaqueomatic.be 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
- 18.158.202.238
18.156.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 35.159.134.130
35.156.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.29.6.131
52.29.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.57.44.57
52.57.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.58.89.11
52.58.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 63.181.75.124
63.180.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for plaqueomatic.be is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- registrar:name srs ab www.namesrs.com
Subdomains
| Subdomain |
|---|
| www.plaqueomatic.be |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-373.awsdns-46.com
- ns-774.awsdns-32.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-1029.awsdns-00.org
- ns-1621.awsdns-10.co.uk
MX records
- plaqueomatic-be.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
- include: mail.zendesk.com
- include: servers.mcsv.net
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from plaqueomatic.be 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: "plaqueomatic.be"})-[: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.