Hostname
crldiagnostics.com
Last fetched
crldiagnostics.com resolves to 104.21.16.37, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. crldiagnostics.com is listed by 2 threat feeds; reconciled level LOW.
Threat posture
1threat score (procedure-native scale)
LOWListed by 2 threat feeds.
- Threat feeds listing this
- 2
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:45:21 GMT
- Last seen on a feed
- Mon, 14 Sep 2026 19:52:08 GMT
Nutrition Label
Resolution chain
- 104.21.16.37
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.21.61.159
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 148.113.8.98
- 172.67.166.20
172.67.160.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.211.142
172.67.208.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
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:303
- Registrant organisation
- ews net pvt.
- Contact emails
- domain@e-web-solutions.net, contact@privacyprotect.org
Subdomains
| Subdomain |
|---|
| lis.crldiagnostics.com |
| lis6.crldiagnostics.com |
| old.crldiagnostics.com |
| rep1.crldiagnostics.com |
| rep2.crldiagnostics.com |
| www.crldiagnostics.com |
Showing 6 of 6 subdomains (6 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- jaxson.ns.cloudflare.com
- monika.ns.cloudflare.com
- owen.ns.cloudflare.com
- sharon.ns.cloudflare.com
- dns1.stabletransit.com
- dns2.stabletransit.com
MX records
- mx.emailarray.com
- mx2.emailarray.com
- us3.mx1.mailhostbox.com
- us3.mx2.mailhostbox.com
- us3.mx3.mailhostbox.com
SPF policy
- redirect: _spf.mailhostbox.com
Threat-feed evidence
History
Related pages
Pivot from crldiagnostics.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: "crldiagnostics.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.