Domain

oauth.vk.com

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

DNS Check HTTP Check Run Full Scan .com TLD

Run a live full scan of oauth.vk.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

93.186.237.1, 95.213.56.1

AAAA

—

TXT

—

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

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.

138.124.65.152:8443 href · ×3

158.160.238.108:443 href · ×3

95.47.161.19:443 href · ×3

185.246.67.20:443 href · ×3

111.88.118.121:443 href · ×3

5.23.48.79:80 href · ×3

144.31.223.68:8080 href · ×2

91.218.228.120:443 href · ×2

37.48.96.202:81 href · ×2

185.9.145.245:443 href · ×2

185.151.242.233:443 href · ×2

80.93.61.243:443 href · ×2

185.219.42.61:443 href · ×2

77.87.215.138:80 href · ×2

176.109.111.241:443 href · ×2

37.18.21.38:443 href · ×2

89.23.108.140:80 href · ×2

178.210.89.10:443 href · ×2

193.124.112.211:8080 href · ×2

37.143.12.53:443 href · ×1

80.78.241.224:80 href · ×1

185.238.201.16:443 href · ×1

80.87.199.239:80 href · ×1

89.111.156.126:443 href · ×1

185.117.153.127:443 href · ×1

93.187.185.89:443 href · ×1

92.255.107.168:80 href · ×1

83.220.170.158:443 href · ×1

91.107.120.7:443 href · ×1

178.218.210.152:443 href · ×1

178.218.210.158:443 href · ×1

45.88.173.176:80 href · ×1

178.159.44.234:80 href · ×1

109.248.222.6:80 href · ×1

91.227.18.170:443 href · ×1

5.59.233.241:8443 href · ×1

151.248.114.145:443 href · ×1

37.46.130.66:80 href · ×1

178.159.44.191:443 href · ×1

95.213.149.194:80 href · ×1

185.133.40.30:80 href · ×1

78.155.219.129:8443 href · ×1

194.67.113.161:443 href · ×1

91.227.34.159:80 href · ×1

37.46.130.66:443 href · ×1

79.174.70.167:443 href · ×1

82.146.54.205:443 href · ×1

147.45.155.168:80 href · ×1

103.228.169.181:443 href · ×1

185.104.113.130: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
A	93.186.237.1	2026-05-25 21:58:50.500	2026-07-28 12:04:07.574
A	95.213.56.1	2026-05-25 21:58:50.500	2026-07-28 12:04:07.574