Check-Host.cc

Domain

deconf.com

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

Run a live full scan of deconf.com

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
1
A/AAAA targets
Subdomains
10
CT + scan + body
Record Types
4
seen in DNS
Observed Certs
2
in our scans

DNS Records

A
159.89.241.107
AAAA
MX
0 mail.deconf.com
NS
pdns1.registrar-servers.com, pdns2.registrar-servers.com
TXT
v=spf1 +mx +a +ip4:46.102.144.5 -all
CNAME
CAA

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
deconf.com 2026-07-28 20:39:29.599
www.deconf.com
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

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

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

64.68.200.71:443 href · ×8
208.85.6.100:443 href · ×4
143.95.33.86:80 href · ×4
216.92.139.43:80 href · ×4
64.68.200.72:80 href · ×4
3.218.209.8:80 href · ×4
141.138.208.158:80 href · ×4
54.80.151.221:80 href · ×4
209.15.110.171:443 href · ×2
93.55.123.13:80 href · ×2
54.179.215.86:443 href · ×2
41.231.36.102:80 href · ×2
52.45.227.50:443 href · ×2
209.133.218.118:80 href · ×2
38.91.58.21:80 href · ×2
185.58.42.205:443 href · ×2
93.55.123.13:443 href · ×2
159.198.44.15:80 href · ×2
14.63.161.55:443 href · ×2
195.62.190.243:443 href · ×2
162.243.94.63:443 href · ×2
189.192.220.70:443 href · ×1
207.90.193.85:443 href · ×1
147.47.107.141:443 href · ×1
116.203.20.195:443 href · ×1
163.178.113.2:443 href · ×1
192.232.247.116:443 href · ×1
52.199.27.95:80 href · ×1
3.82.45.117:80 href · ×1
38.242.159.104:443 href · ×1
140.227.161.58:443 href · ×1
107.161.30.188:443 href · ×1
195.62.190.244:443 href · ×1
208.109.73.139:80 href · ×1
79.96.80.225:80 href · ×1
138.201.185.81:80 href · ×1
94.46.180.41:9443 href · ×1
45.227.160.248:443 href · ×1
111.89.138.235:80 href · ×1
104.207.95.211:443 href · ×1
104.156.56.14:443 href · ×1
138.68.134.212:80 href · ×1
220.135.58.69:443 href · ×1
217.174.152.175:443 href · ×1
173.236.252.230:80 href · ×1
203.101.225.187:80 href · ×1
5.196.113.27:443 href · ×1
52.237.29.217:80 href · ×1
13.228.99.255:80 href · ×1
139.59.107.39:443 href · ×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 pdns2.registrar-servers.com 2026-05-26 02:22:42.939 2026-07-28 20:39:29.599
A 159.89.241.107 2026-05-26 02:22:42.939 2026-07-28 20:39:29.599
NS pdns1.registrar-servers.com 2026-05-26 02:22:42.939 2026-07-28 20:39:29.599
MX 0 mail.deconf.com 2026-05-26 02:22:42.939 2026-07-28 20:39:29.599
TXT v=spf1 +mx +a +ip4:46.102.144.5 -all 2026-05-26 02:22:42.939 2026-07-28 20:39:29.599