being.com
SPF only
Amazon Web Services qq.com
DNS, hosting, email and name analysis are live. Registration data, the home-page probe, the archive lookup and the other-TLD check are being fetched in the background; this page refreshes itself in a few seconds.
Registration
Fetching the registry record…
DNS
| Type | Value |
|---|---|
| NS | viddy.ns.cloudflare.com · violet.ns.cloudflare.com |
| A | 216.150.1.193 |
| A | 216.150.16.193 |
| MX | 5 mxbiz1.qq.com |
| MX | 10 mxbiz2.qq.com |
| TXT | v=spf1 include:spf.mail.qq.com ~all |
| TXT | edaa134e-f2b2-487c-aac2-3433372fe706=63ac812132a107ee5cb15c853e03fb277b61b5d48607bbfdff7b1e429a111f22 |
| SOA | viddy.ns.cloudflare.com dns.cloudflare.com serial 2417681573 |
Certificates
- First certificate seen
- 2026-10-13 21:50 UTC since dot.bi started watching
- Last certificate seen
- 2026-10-13 21:50 UTC
- Certificates observed
- 4
- Issuers
- Google Trust Services
Hosting
- IP
- 216.150.1.193
- Network
- AS16509 · AMAZON-02 - Amazon.com, Inc., US
- Provider
- Amazon Web Services
- Country
- US (network registration, not server location)
- CDN
- none detected
- IPv6
- no
Web
Probing the home page…
SPF only SPF is published but there is no DMARC policy.
- Provider
- qq.com
- SPF
- present all: softfail
- DMARC
- missing
- DKIM
- not found common selectors only
Age
- First capture
- looking up…
- Years archived
- —
- Registry created
- —
- In dot.bi since
- 2026-10-13 · Certificate Transparency
Name analysis
Same name, other TLDs
Checking the same name on other TLDs…
History observed by dot.bi
A record changed: 216.150.1.1, 216.150.16.1 → 216.150.1.193, 216.150.16.193
First observed by dot.bi · source: ct