Hostname
nead.be
Last fetched
nead.be resolves to 16 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in DE.
Nutrition Label
Resolution chain
nead.be resolves to 16 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 16.12.24.40 | 16.12.24.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.5.135.57 | 3.5.135.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.5.136.175 | 3.5.136.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.5.138.141 | 3.5.138.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.5.138.239 | 3.5.138.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.5.138.44 | 3.5.138.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.5.138.45 | 3.5.138.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.5.138.98 | 3.5.138.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.5.139.49 | 3.5.139.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.5.139.86 | 3.5.139.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 52.219.169.188 | 52.219.169.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 52.219.169.216 | 52.219.169.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 52.219.170.232 | 52.219.170.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 52.219.171.100 | 52.219.171.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 52.219.75.218 | 52.219.75.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 52.219.75.36 | 52.219.75.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
WHOIS identity
No WHOIS records are currently associated with nead.be in WhisperGraph.
Subdomains
2 observed subdomains of nead.be.
| Subdomain |
|---|
| kba.nead.be |
| scaldis.nead.be |
Threat posture
History
Mail and authentication
MX records
SPF policy
2 SPF mechanisms authorising senders for nead.be.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | my.billit.be |
| SPF_INCLUDE | spf.protection.outlook.com |
Related pages
Pivot deeper into the graph from nead.be.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "nead.be"})-[: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.