Hostname
denguetaskforce.com
Last fetched
denguetaskforce.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
denguetaskforce.com resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 18.161.134.111 | 18.161.134.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.161.134.119 | 18.161.134.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.161.134.128 | 18.161.134.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.161.134.18 | 18.161.134.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.244.28.124 | 18.244.28.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
| 18.244.28.33 | 18.244.28.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
| 18.244.28.47 | 18.244.28.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
| 18.244.28.72 | 18.244.28.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of denguetaskforce.com owner
- Contact emails
Subdomains
5 observed subdomains of denguetaskforce.com.
Web-graph footprint
Distinct hostnames that link to or from denguetaskforce.com in the public web crawl.
6 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
1 SPF mechanism authorising senders for denguetaskforce.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | spf.protection.outlook.com |
Related pages
Pivot deeper into the graph from denguetaskforce.com.
- IP · 18.161.134.111
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · 2d14b90d-5429-44fc-b42c-d20ae7abe342@identity-protect.org
- TLD · .com
- Browse hostnames · de…
- 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: "denguetaskforce.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.