Hostname
nw18.com
Last fetched
nw18.com resolves to 4 IPv4 addresses operated by AKAMAI-AS - Akamai Technologies, Inc. in DE. WHOIS lists iana:303 as the registrar.
Nutrition Label
Resolution chain
nw18.com resolves to 4 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.85.250.152 | 104.85.250.0/23 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | DE |
| 184.29.108.191 | 184.29.108.0/23 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | ZA |
| 23.197.135.5 | 23.197.128.0/20 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | DE |
| 23.47.24.217 | 23.47.16.0/20 | AS16625 | AKAMAI-AS - Akamai Technologies, Inc. | US |
WHOIS identity
- Registrar
- iana:303
- Organization
- manage domain
- Contact emails
Subdomains
75 observed subdomains of nw18.com.
Showing 25 of 75. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from nw18.com in the public web crawl.
109 sites link to this hostname.
4 sites linked to from this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
SPF policy
9 SPF mechanisms authorising senders for nw18.com.
| Mechanism | Target |
|---|---|
| SPF_EXISTS | %{i}.spf.hc1534-53.ap.iphmx.com |
| SPF_INCLUDE | _spf.atlassian.net |
| SPF_INCLUDE | _spf.eu.mailgun.org |
| SPF_INCLUDE | _spf1.mailgun.org |
| SPF_INCLUDE | _spf2.mailgun.org |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 103.167.80.80/32 |
| SPF_MX | nw18.com |
Related pages
Pivot deeper into the graph from nw18.com.
- IP · 104.85.250.152
- ASN · AS16625AKAMAI-AS - Akamai Technologies, Inc.
- Registrar · iana:303
- Country · DE
- Email · rajdomainz@gmail.com
- TLD · .com
- Browse hostnames · nw…
- 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: "nw18.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.