Domain Intelligence Report
Gathering intelligence... (0/12)
DNS
WHOIS
Security
Email
DNSSEC
Threats
Deliverability
SSL/TLS
HTTP
Tech Stack
Subdomains
Archive
Safe
Checking…no attacks or spoofing
Up
Checking…reachable and responding
Right
Set up Page Watchit is what it is
Ready
Checking…you see what's coming
Outline
Gathering data — check results will appear here as they complete.
DNS Records
WHOIS
Then vs Nownew
No card for this name. We compare then and now for domains that are in the top million and had an AboutUs page. That says nothing about this domain’s age or safety.
Check what it is now →SSL/TLS
Security
Email Auth
DNSSEC
Tech Stack
HTTP / Headers
Threats
Zone census
Subdomains
Web Archive
Deliverability
IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for diflag.com. Run the check on aaaa.bot →
Lineage
Our records: Oct 18, 2013 → Nov 4, 2026DNS at Cloudflare · 8 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
DNS provider
3 earlier
- dnspod.netOct 2013 – Apr 2018
- CloudflareNOWSeen from Nov 2026
- foundationapi.comJan 2016
- ezdnscenter.comMar – Apr 2016
- judns.comAug – Sep 2026
- ename.netSep 2026
- kouming.netOct 2026
What changed (latest 8 of 10)
- DNS moved to Cloudflare between Oct 31, 2026 and Nov 1, 2026ns1.kouming.net, ns2.kouming.net → alexandra.ns.cloudflare.com, clint.ns.cloudflare.com.
- Missing from the zone file, then back between Sep 23, 2026 and Oct 31, 2026Listed on 2026-09-23, missing from the next held snapshot, listed again on 2026-10-31. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to kouming.net between Sep 23, 2026 and Oct 31, 2026exp1.ename.net, exp2.ename.net → ns1.kouming.net, ns2.kouming.net.
- DNS moved to ename.net between Sep 1, 2026 and Sep 2, 2026ns1.judns.com, ns2.judns.com → exp1.ename.net, exp2.ename.net.
- DNS moved to judns.com between Apr 3, 2018 and Aug 5, 2026f1g1ns1.dnspod.net, f1g1ns2.dnspod.net → ns1.judns.com, ns2.judns.com.
- DNS moved to dnspod.net between Apr 1, 2016 and Apr 3, 2018ns1.ezdnscenter.com, ns2.ezdnscenter.com, ns3.ezdnscenter.com, ns4.ezdnscenter.com, ns5.ezdnscenter.com, ns6.ezdnscenter.com → f1g1ns1.dnspod.net, f1g1ns2.dnspod.net.
- Missing from the zone file, then back between Jan 1, 2016 and Mar 1, 2016Listed on 2016-01-01, missing from the next held snapshot, listed again on 2016-03-01. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to ezdnscenter.com between Jan 1, 2016 and Mar 1, 2016dns10.parkpage.foundationapi.com, dns11.parkpage.foundationapi.com → ns1.ezdnscenter.com, ns2.ezdnscenter.com, ns3.ezdnscenter.com, ns4.ezdnscenter.com, ns5.ezdnscenter.com, ns6.ezdnscenter.com.
Solid bar: the stretch we observed that name. Dot: a single sighting. Dotted line: no record between sightings of the same name. Nothing is drawn between different names.
DNS provider, registry zone files: 109 .com zone-file snapshots held, 2013-10-18 to 2026-11-04.
Want to know when diflag.com changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.