Check-Host.cc

Domain

mx2.law

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

Run a live full scan of mx2.law

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
100
A/AAAA targets
Subdomains
56
CT + scan + body
Record Types
seen in DNS
Observed Certs
2
in our scans

DNS Records

A
AAAA
MX
NS
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

Subject: court-reporting.api.mx2.law
Issuer: Amazon RSA 2048 M03
SANs: court-reporting.api.mx2.law
Subject: referral-sync.api.mx2.law
Issuer: Amazon RSA 2048 M04
SANs: referral-sync.api.mx2.law
Subject: quaero.api.mx2.law
Issuer: Amazon RSA 2048 M02
SANs: quaero.api.mx2.law
Subject: dec-page.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: dec-page.api.mx2.law
Subject: search-api.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: search-api.api.mx2.law
Subject: docket-sync.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: docket-sync.api.mx2.law
Subject: docket-sync.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: docket-sync.api.mx2.law
Subject: llm.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: llm.api.mx2.law
Subject: samuel-sse.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: samuel-sse.api.mx2.law
Subject: samuel-sse.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: samuel-sse.api.mx2.law
Subject: vendor-integrations.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: vendor-integrations.api.mx2.law
Subject: case-worth.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: case-worth.api.mx2.law
Subject: demand-generate.api.mx2.law
Issuer: Amazon RSA 2048 M03
SANs: demand-generate.api.mx2.law
Subject: pdf.api.mx2.law
Issuer: Amazon RSA 2048 M04
SANs: pdf.api.mx2.law
Subject: sources.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: sources.api.mx2.law
Subject: classifier.api.mx2.law
Issuer: Amazon RSA 2048 M04
SANs: classifier.api.mx2.law
Subject: quaero.api.mx2.law
Issuer: Amazon RSA 2048 M02
SANs: quaero.api.mx2.law
Subject: page.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: page.api.mx2.law
Subject: responder.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: responder.api.mx2.law
Subject: enterprise.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: enterprise.api.mx2.law
Subject: nrr.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: nrr.api.mx2.law
Subject: sf-sync.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: sf-sync.api.mx2.law
Subject: docket-sync.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: docket-sync.api.mx2.law
Subject: file.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: file.api.mx2.law
Subject: responder.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: responder.api.mx2.law
Subject: case-like-mine.api.mx2.law
Issuer: Amazon RSA 2048 M04
SANs: case-like-mine.api.mx2.law
Subject: court-reporting.api.mx2.law
Issuer: Amazon RSA 2048 M03
SANs: court-reporting.api.mx2.law
Subject: responder.api.mx2.law
Issuer: Amazon RSA 2048 M01
SANs: responder.api.mx2.law
Subject: demand-generate.api.mx2.law
Issuer: Amazon RSA 2048 M03
SANs: demand-generate.api.mx2.law
Subject: quaero.api.mx2.law
Issuer: Amazon RSA 2048 M02
SANs: quaero.api.mx2.law

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.

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.