Hostname
njdisa.com
Last fetched
njdisa.com resolves to 104.21.96.18, announced in 104.21.96.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. njdisa.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
- 104.21.96.18
104.21.96.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.150.66
172.67.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 91.209.253.12
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.13
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.14
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.9
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.10
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 91.209.253.11
91.209.253.0/24 · CLOUDFLARESPECTRUM - Cloudflare London, LLC · Riyadh, SA
- 162.159.143.27
162.159.128.0/19 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.3.23
172.66.0.0/22 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:625
- Registrant organisation
- nawaf hariri
Subdomains
| Subdomain |
|---|
| go.njdisa.com |
| server.njdisa.com |
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns1.salla.cloud
- ns2.salla.cloud
MX records
- mx.zoho.com
- mx2.zoho.com
- mx3.zoho.com
SPF policy
- include: zohomail.com
Threat-feed evidence
History
Related pages
Pivot from njdisa.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: "njdisa.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.