d64.org was registered with Domain.com - Network Solutions, LLC on 12 Sept 2000. Its SSL certificate from Google Trust Services is valid until 23 Dec 2026, and the site supports HTTP/3. WOT's community rates its safety good (61/100).
On-page basics for the homepage.
Networks cache previews — changes can take time to show.
What security vendors and the WOT community say about this domain.
3 of 5 protections set up
Lists the servers allowed to send email for this domain.
v=spf1 include:_spf.ps.computerlogicgroup.com include:_spf.google.com include:_spf.sparkpostmail.com include:spf.constantcontact.com include:customerspf.schoolmessenger.com ip4:23.21.109.197 ip4:23.21.109.212 ip4:147.160.167.0/26 ip4:76.73.191.199/32 ~allSigns outgoing mail so receivers can verify it.
selector google._domainkeyPolicy is “quarantine”: spoofed mail goes to spam.
v=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]; sp=none; aspf=r;Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
4 of 6 recommended headers
Forces HTTPS on future visits.
Limits where scripts can load from — the main defence against XSS.
Stops the site being framed for clickjacking.
Prevents browsers guessing file types.
Which AI crawlers this site allows, and whether it publishes an llms.txt.
From robots.txt. “Partly blocked”: kept out of some pages, not the homepage. Not every crawler follows it. llms.txt is an optional guide some sites publish for AI assistants — it is not a ranking factor.
Pages and files that show who runs the site and how it handles data.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
268 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| d64.lat | Other extension | 19 Oct 2026 | Active website | Report → |
| d64.casino | Other extension | 18 Oct 2026 | Active website | Report → |
| d64.cam | Other extension | 17 Oct 2026 | Active website | Report → |
| d64.cn | Other extension | 5 Oct 2026 | No website | Report → |
| d46.xyz | Typo | 30 Sept 2026 | Active website | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is d64.org’s name taken on other extensions?
2 technologies detected across 2 categories.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address d64.org resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| d64.org | 104.21.39.5 | 300 |
| d64.org | 172.67.141.204 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| d64.org | 2606:4700:3031::ac43:8dcc | 300 |
| d64.org | 2606:4700:3035::6815:2705 | 300 |
| Host | Mail server | TTL |
|---|---|---|
| d64.org | 1 aspmx.l.google.com | 300 |
| d64.org | 5 alt1.aspmx.l.google.com | 300 |
| d64.org | 5 alt2.aspmx.l.google.com | 300 |
| d64.org | 10 alt3.aspmx.l.google.com | 300 |
| d64.org | 10 alt4.aspmx.l.google.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| d64.org | max.ns.cloudflare.com | 86400 |
| d64.org | zoe.ns.cloudflare.com | 86400 |
| Host | Text | TTL |
|---|---|---|
| d64.org | "_dpytk5n0yc01r0k7fduihbbew2u64ff" | 300 |
| d64.org | "_s7nr1dyjvcaciktwjhcfbhl4q7zymnc" | 300 |
| d64.org | "090sr98mr89vkyntkq518w43mdtwlj3f" | 300 |
| d64.org | "apple-domain-verification=tzXWv1p6n9E8SatA" | 300 |
| d64.org | "bm6wwf2hq1q0b36pzgqgg9w0znvlbwyk" | 300 |
| d64.org | "campussuite-domain-verification=95291a23f4283784dfa74f237ee34488" | 300 |
| d64.org | "google-site-verification=kcSHHG1ekg_4gpFICawBtbpK44Oy7OOcvm4YvEOuSDo" | 300 |
| d64.org | "jamf-site-verification=6Blor5NHLKQZoc1HTQTEFw" | 300 |
| d64.org | "MS=ms24528641" | 300 |
| d64.org | "nordpass-domain-verification=98522b6be30ff232eaafab6d3e3743ea62d23c03f4aed4ec0758306f41faa179" | 300 |
| d64.org | "v=spf1 include:_spf.ps.computerlogicgroup.com include:_spf.google.com include:_spf.sparkpostmail.com include:spf.constantcontact.com include:customerspf.schoolmessenger.com ip4:23.21.109.197 ip4:23.21.109.212 ip4:147.160.167.0/26 ip4:76.73.191.199/32 ~all" | 300 |
| d64.org | "ZOOM_verify_YeUuejrGSsaQpJcjWVxwEg" | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| d64.org | max.ns.cloudflare.com dns.cloudflare.com 2415913763 10000 2400 604800 1800 | 1800 |
Other domains served from 172.64.80.1. Normal for shared hosting and CDNs.
No reviews yet. Used d64.org? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
WOT's community rates d64.org good for safety (61/100). Its SSL certificate is valid until 23 Dec 2026. See Security →
d64.org is registered through Domain.com - Network Solutions, LLC. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expires on 12 Sept 2027 — in 10 months. See Overview →
d64.org was registered on 12 Sept 2000, making it 26 years old. See Overview →
d64.org is served from 2 IP addresses, mainly on AS13335. See Hosting →
We detected 2 technologies, including Google Analytics and jQuery. See Built with →
Raw registry data for d64.org. May be redacted by privacy services.
Domain Name: d64.org Registry Domain ID: REDACTED Registrar WHOIS Server: whois.domain.com Registrar URL: http://www.domain.com Updated Date: 2026-08-28T08:35:36Z Creation Date: 2000-09-12T23:17:55Z Registry Expiry Date: 2027-09-12T23:17:55Z Registrar: Domain.com - Network Solutions, LLC Registrar IANA ID: 886 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.8777228662 Domain Status: ok https://icann.org/epp#ok Name Server: max.ns.cloudflare.com Name Server: zoe.ns.cloudflare.com DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-30T07:40:30Z <<< For more information on Whois status codes, please visit https://icann.org/epp Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
The first response from http://www.d64.org, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with d64.org. Data is collected independently from public sources and some figures are estimates, provided for information only.
Controls how much of the URL is shared with other sites.
Restricts camera, microphone and other browser features.
From the homepage's response, https://www.d64.org/
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 30 Oct 2026.