Check-Host.cc

Domain

foreceipt.com

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

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

DNS Records

A
3.82.80.13
AAAA
MX
1 aspmx.l.google.com, 10 alt3.aspmx.l.google.com, 10 alt4.aspmx.l.google.com, 5 alt1.aspmx.l.google.com, 5 alt2.aspmx.l.google.com
NS
ns-1491.awsdns-58.org, ns-2031.awsdns-61.co.uk, ns-318.awsdns-39.com, ns-775.awsdns-32.net
TXT
MS=A1CD486F5A446510DAB84154AA9960F68E77F3DF, QhCMeB7XIdfchhZU7Q3cHF5L3qjSloF74BJLi/o2Uew=, firebase=foreceipt, firebase=foreceipt-firestore, google-site-verification=GF7lgrrfB85n1H2125awgUrjg0KfTNHeA5Q77sPWa_k, v=spf1 a mx ~all, v=spf1 include:_spf.firebasemail.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
app.foreceipt.com
1970-01-01 00:00:00.000
foreceipt.com 2026-05-26 12:37:21.914

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.

3.82.80.13:80 href · ×1
3.82.80.13:80 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 ns-1491.awsdns-58.org 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
NS ns-775.awsdns-32.net 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
TXT v=spf1 include:_spf.firebasemail.com ~all 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
TXT MS=A1CD486F5A446510DAB84154AA9960F68E77F3DF 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
NS ns-318.awsdns-39.com 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
A 3.82.80.13 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
TXT firebase=foreceipt-firestore 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
TXT google-site-verification=GF7lgrrfB85n1H2125awgUrjg0KfTNHeA5Q77sPWa_k 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
MX 5 alt2.aspmx.l.google.com 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
MX 10 alt4.aspmx.l.google.com 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
MX 1 aspmx.l.google.com 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
TXT v=spf1 a mx ~all 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
MX 5 alt1.aspmx.l.google.com 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
MX 10 alt3.aspmx.l.google.com 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
NS ns-2031.awsdns-61.co.uk 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
TXT QhCMeB7XIdfchhZU7Q3cHF5L3qjSloF74BJLi/o2Uew= 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914
TXT firebase=foreceipt 2026-05-26 12:37:21.914 2026-05-26 12:37:21.914