Check-Host.cc

Domain

aus.vet

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

Run a live full scan of aus.vet

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

DNS Records

A
13.239.213.147, 13.54.66.127, 3.104.139.54, 3.24.140.94, 3.24.195.154, 52.62.109.130, 52.62.176.249, 54.206.185.180
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
ns-1122.awsdns-12.org, ns-1929.awsdns-49.co.uk, ns-77.awsdns-09.com, ns-807.awsdns-36.net
TXT
google-site-verification=AO5mHn3VIsuTrM2k6QRqbZGOPlfjYB0uJK9gOmK1Pms
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: *.stockhaus.vet
Issuer: Sectigo Public Server Authentication CA DV R36
SANs: *.stockhaus.vet, stockhaus.vet
Subject: *.aus.vet
Issuer: Amazon RSA 2048 M01
SANs: *.aus.vet, aus.vet
Subject: *.aus.vet
Issuer: Amazon RSA 2048 M04
SANs: *.aus.vet, aus.vet
Subject: *.aus.vet
Issuer: Amazon RSA 2048 M04
SANs: *.aus.vet, aus.vet
Subject: *.aus.vet
Issuer: Amazon RSA 2048 M01
SANs: *.aus.vet, aus.vet

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.

6cd535ac57fd9f79… google · xenon2026h2
Subject: *.aus.vet
Issuer: Amazon RSA 2048 M01
SANs: *.aus.vet, aus.vet
Valid: 2026-04-04 00:00:00 → 2026-10-18 23:59:59
326483d7ab0e3a90… google · xenon2026h2
Subject: *.aus.vet
Issuer: Amazon RSA 2048 M04
SANs: *.aus.vet, aus.vet
Valid: 2026-03-26 00:00:00 → 2026-10-09 23:59:59
78edb697758d8a3e… google · argon2026h2
Subject: *.aus.vet
Issuer: Amazon RSA 2048 M02
SANs: *.aus.vet, aus.vet
Valid: 2025-09-03 00:00:00 → 2026-10-02 23:59:59
7928a33b85768b90… google · argon2026h2
Subject: *.aus.vet
Issuer: Amazon RSA 2048 M02
SANs: *.aus.vet, aus.vet
Valid: 2025-09-03 00:00:00 → 2026-10-02 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.