Check-Host.cc

Domain

telfinity.host

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

Run a live full scan of telfinity.host

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
18.239.105.110, 18.239.105.39, 18.239.105.87, 18.239.105.98, 54.192.35.120, 54.192.35.122, 54.192.35.29, 54.192.35.35
AAAA
2600:9000:2130:c600:2:a993:bec0:93a1, 2600:9000:213f:4400:2:a993:bec0:93a1, 2600:9000:213f:7200:2:a993:bec0:93a1, 2600:9000:213f:aa00:2:a993:bec0:93a1, 2600:9000:213f:c800:2:a993:bec0:93a1, 2600:9000:213f:d200:2:a993:bec0:93a1, 2600:9000:213f:dc00:2:a993:bec0:93a1, 2600:9000:213f:de00:2:a993:bec0:93a1
MX
NS
ns-1436.awsdns-51.org, ns-153.awsdns-19.com, ns-1974.awsdns-54.co.uk, ns-938.awsdns-53.net
TXT
MS=ms35538315
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

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

Tech Stack

Tech detection pending

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

TLS Certificates

Subject: *.telfinity.host
Issuer: Amazon RSA 2048 M04
SANs: *.telfinity.host, telfinity.host
Subject: *.telfinity.host
Issuer: Amazon RSA 2048 M04
SANs: *.telfinity.host, telfinity.host
Subject: *.telfinity.host
Issuer: Amazon RSA 2048 M04
SANs: *.telfinity.host, telfinity.host

IPs Citing This Domain

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

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.

CT-Log Evidence

Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.

16431f6660f35cae… google · xenon2026h2
Subject: *.telfinity.host
Issuer: Amazon RSA 2048 M04
SANs: *.telfinity.host, telfinity.host
Valid: 2026-04-07 00:00:00 → 2026-10-21 23:59:59
9f6392224dfe8697… google · xenon2026h2
Subject: *.telfinity.host
Issuer: Amazon RSA 2048 M04
SANs: *.telfinity.host, telfinity.host
Valid: 2026-04-07 00:00:00 → 2026-10-21 23:59:59

Threat Intelligence

Domain threat-intel pending

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

History

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.