daiconnect.com
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of daiconnect.com
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
DNS Records
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 |
|---|---|---|
| daiconnect.com | 2026-06-20 06:10:06.656 | |
| demo.cdn.daiconnect.com | 2026-07-21 22:11:53.773 | |
| abc.us.demo.daiconnect.com | 2026-06-04 08:06:06.104 | |
| cs.daiconnect.com | 1970-01-01 00:00:00.000 | |
| monitoring.daiconnect.com | 1970-01-01 00:00:00.000 | |
| rtl-radio.cdn.daiconnect.com | 1970-01-01 00:00:00.000 | |
| us.demo.daiconnect.com | 2026-07-25 03:46:19.906 |
Tech Stack
Tech detection pending
Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.
TLS Certificates
IPs Citing This Domain
Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.
Origin / IP-Leak
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 |
|---|---|---|---|
| MX | 5 alt1.aspmx.l.google.com | 2026-05-26 00:17:38.499 | 2026-06-20 06:10:06.656 |
| MX | 10 alt3.aspmx.l.google.com | 2026-05-26 00:17:38.499 | 2026-06-20 06:10:06.656 |
| NS | ns-1046.awsdns-02.org | 2026-05-26 00:17:38.499 | 2026-06-20 06:10:06.656 |
| A | 18.202.39.52 | 2026-05-26 00:17:38.499 | 2026-05-26 07:16:22.366 |
| NS | ns-854.awsdns-42.net | 2026-05-26 00:17:38.499 | 2026-06-20 06:10:06.656 |
| NS | ns-317.awsdns-39.com | 2026-05-26 00:17:38.499 | 2026-06-20 06:10:06.656 |
| A | 34.241.42.21 | 2026-05-26 00:17:38.499 | 2026-06-02 13:41:53.693 |
| NS | ns-1662.awsdns-15.co.uk | 2026-05-26 00:17:38.499 | 2026-06-20 06:10:06.656 |
| TXT | google-site-verification=iJ3BTEUwe-kvJ--2KcjIeF9NY_PtoLqp3jotdvK5Dvc | 2026-05-26 00:17:38.499 | 2026-06-20 06:10:06.656 |
| MX | 5 alt2.aspmx.l.google.com | 2026-05-26 00:17:38.499 | 2026-06-20 06:10:06.656 |
| A | 52.209.22.53 | 2026-05-26 00:17:38.499 | 2026-05-26 07:16:22.366 |
| MX | 10 alt4.aspmx.l.google.com | 2026-05-26 00:17:38.499 | 2026-06-20 06:10:06.656 |
| MX | 1 aspmx.l.google.com | 2026-05-26 00:17:38.499 | 2026-06-20 06:10:06.656 |
| A | 46.51.188.56 | 2026-06-02 13:41:53.693 | 2026-06-02 13:41:53.693 |
| A | 108.132.43.224 | 2026-06-02 13:41:53.693 | 2026-06-02 13:41:53.693 |
| A | 54.154.66.108 | 2026-06-04 21:15:58.011 | 2026-06-04 21:15:58.011 |
| A | 52.17.167.206 | 2026-06-04 21:15:58.011 | 2026-06-04 21:15:58.011 |
| A | 54.220.129.137 | 2026-06-04 21:15:58.011 | 2026-06-04 21:15:58.011 |
| A | 34.248.140.14 | 2026-06-17 10:30:58.191 | 2026-06-17 10:30:58.191 |
| A | 3.248.27.64 | 2026-06-17 10:30:58.191 | 2026-06-17 10:30:58.191 |
| A | 52.31.204.44 | 2026-06-17 10:30:58.191 | 2026-06-17 10:30:58.191 |
| A | 52.211.9.250 | 2026-06-20 06:10:06.656 | 2026-06-20 06:10:06.656 |
| A | 34.243.149.208 | 2026-06-20 06:10:06.656 | 2026-06-20 06:10:06.656 |
| A | 52.18.155.155 | 2026-06-20 06:10:06.656 | 2026-06-20 06:10:06.656 |