Check-Host.cc

Domain

digitaljournal.com

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

Run a live full scan of digitaljournal.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
6
A/AAAA targets
Subdomains
19
CT + scan + body
Record Types
4
seen in DNS
Observed Certs
11
in our scans

DNS Records

A
104.17.46.19, 104.17.47.19
AAAA
MX
1 aspmx.l.google.com, 10 aspmx2.googlemail.com, 10 aspmx3.googlemail.com, 5 alt1.aspmx.l.google.com, 5 alt2.aspmx.l.google.com
NS
carioca.ns.cloudflare.com, ernest.ns.cloudflare.com
TXT
google-site-verification=feEUeDlgbsHSHtq9GPtlX0eV5upnbvDtEVZ4C1n2lPY, google-site-verification=jBC8n2aO4MvQOf1Tqy879yqJcQ2CcFCEqiuX4GwG0sY, linkedin-site-verification=b0cea2bd-d061-497a-972d-44f5ac5c666e, v=spf1 include:45739551.spf06.hubspotemail.net include:_spf.google.com ~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
if.digitaljournal.com 2026-07-23 18:37:44.075
digitaljournal.com 2026-07-15 20:04:13.980
www.digitaljournal.com 2026-07-28 06:23:49.431
store.digitaljournal.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.

185.43.220.221:443 href · ×1
188.166.7.54:8443 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
A 104.17.46.19 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
TXT v=spf1 include:45739551.spf06.hubspotemail.net include:_spf.google.com ~all 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
MX 10 aspmx3.googlemail.com 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
NS ernest.ns.cloudflare.com 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
NS carioca.ns.cloudflare.com 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
MX 10 aspmx2.googlemail.com 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
TXT google-site-verification=feEUeDlgbsHSHtq9GPtlX0eV5upnbvDtEVZ4C1n2lPY 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
A 104.17.47.19 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
MX 5 alt2.aspmx.l.google.com 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
MX 1 aspmx.l.google.com 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
MX 5 alt1.aspmx.l.google.com 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
TXT google-site-verification=jBC8n2aO4MvQOf1Tqy879yqJcQ2CcFCEqiuX4GwG0sY 2026-05-26 05:18:44.431 2026-07-15 20:04:13.980
TXT linkedin-site-verification=b0cea2bd-d061-497a-972d-44f5ac5c666e 2026-06-22 21:21:54.137 2026-07-15 20:04:13.980