Check-Host.cc

Domain

hazardous.org

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

Run a live full scan of hazardous.org

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now
Hosting IPs
2
A/AAAA targets
Subdomains
8
CT + scan + body
Record Types
6
seen in DNS
Observed Certs
3
in our scans

DNS Records

A
46.23.92.13
AAAA
2a03:6000:6f71:603::13
MX
10 in1-smtp.messagingengine.com, 20 in2-smtp.messagingengine.com
NS
ns1.dnsimple-edge.com, ns2.dnsimple-edge.net, ns3.dnsimple-edge.io, ns4.dnsimple-edge.org
TXT
v=spf1 include:spf.messagingengine.com ?all
CNAME
CAA
0 issue "letsencrypt.org"

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Subdomain Resolves to Last seen
hawkins.hazardous.org 2026-05-26 20:51:06.346
hazardous.org 2026-05-26 20:51:06.346
www.hazardous.org 2026-05-26 20:51:06.346
alertmanager.hazardous.org
1970-01-01 00:00:00.000
blackboxexporter.hazardous.org
1970-01-01 00:00:00.000
goneb-bot.hazardous.org
1970-01-01 00:00:00.000
karma.hazardous.org
1970-01-01 00:00:00.000
p.hazardous.org
1970-01-01 00:00:00.000

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Subject: hazardous.org
Issuer: R12
SANs: felix.kronlage.damme.rs, felix.kronlage.de, hawkins.hazardous.org, hazardous.org, kronlage.damme.rs, www.hazardous.org

IPs Citing This Domain

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

46.23.92.13:443 href · ×8
46.23.92.13:443 canonical · ×1

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
NS ns4.dnsimple-edge.org 2026-05-26 20:51:06.346 2026-05-26 20:51:06.346
MX 20 in2-smtp.messagingengine.com 2026-05-26 20:51:06.346 2026-05-26 20:51:06.346
A 46.23.92.13 2026-05-26 20:51:06.346 2026-05-26 20:51:06.346
TXT v=spf1 include:spf.messagingengine.com ?all 2026-05-26 20:51:06.346 2026-05-26 20:51:06.346
NS ns1.dnsimple-edge.com 2026-05-26 20:51:06.346 2026-05-26 20:51:06.346
MX 10 in1-smtp.messagingengine.com 2026-05-26 20:51:06.346 2026-05-26 20:51:06.346
AAAA 2a03:6000:6f71:603::13 2026-05-26 20:51:06.346 2026-05-26 20:51:06.346
NS ns2.dnsimple-edge.net 2026-05-26 20:51:06.346 2026-05-26 20:51:06.346
CAA 0 issue "letsencrypt.org" 2026-05-26 20:51:06.346 2026-05-26 20:51:06.346
NS ns3.dnsimple-edge.io 2026-05-26 20:51:06.346 2026-05-26 20:51:06.346