popyard.org

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200SafeSSL: 34 days left23 years old

One re-check per domain each UTC day.

70

popyard.org was registered on 11 Jul 2003 via Cloudflare, Inc. and the registry expiry is 11 Jul 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/popyard.org.

popyard.org publishes 2 nameservers. DNSSEC is not signed.

popyard.org has 2 IPv4 addresses (104.21.90.224, 172.67.205.173) and 2 IPv6 addresses (2606:4700:3032::6815:5ae0, 2606:4700:3036::ac43:cdad). The geolocation database places 104.21.90.224 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 34 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for popyard.org in the checks that ran.

Domain · RDAP/WHOIS

popyard.org was registered on 11 Jul 2003 via Cloudflare, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/popyard.org.

Registeredsince 11 Jul 2003
Created11 July 2003
Updated12 August 2026
Expires11 July 2027
RegistrarCloudflare, Inc.
Statusclient transfer prohibited
Nameserversgabe.ns.cloudflare.com, may.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.publicinterestregistry.org/rdap/domain/popyard.org

popyard.org carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.

Nameserver gabe.ns.cloudflare.com is published for popyard.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/popyard.org.

Nameserver may.ns.cloudflare.com is published for popyard.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/popyard.org.

DNS

popyard.org has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.21.90.224, 172.67.205.173
AAAA2606:4700:3032::6815:5ae0, 2606:4700:3036::ac43:cdad
NSgabe.ns.cloudflare.com, may.ns.cloudflare.com
MXroute1.mx.cloudflare.net (45), route2.mx.cloudflare.net (46), route3.mx.cloudflare.net (73)
SPFpresent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at popyard.org is "v=spf1 include:_spf.mx.cloudflare.net ~all".

IPv4 address 104.21.90.224 answers for popyard.org at resolver 1.1.1.1:53.

IPv4 address 172.67.205.173 answers for popyard.org at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3032::6815:5ae0 answers for popyard.org at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3036::ac43:cdad answers for popyard.org at resolver 1.1.1.1:53.

Mail exchanger route1.mx.cloudflare.net has preference 45.

Mail exchanger route2.mx.cloudflare.net has preference 46.

Mail exchanger route3.mx.cloudflare.net has preference 73.

Hosting and geo

popyard.org is placed in Toronto, Canada by the local geolocation database (db-ip).

Address104.21.90.224
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for popyard.org is valid, with 34 days left and 1 subject alternative name. Source: tls:443.

IssuerWE1
Subjectpopyard.org
Valid from6 September 2026
Valid until5 December 2026
Days left34
SAN count1
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: popyard.org.

Tech stack

Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.

  • Cloudflare · CDN
  • HTTP/3 · Miscellaneous

Cloudflare is filed under CDN.

HTTP/3 is filed under Miscellaneous.

On-page checks

The homepage returned HTTP 200 in 119 ms. The target title is 0 characters and the page has 0 H1 headings.

Status200
TTFB119 ms
Title length0 no
Quoted titlenone
Meta descriptionnone no
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Languageen
Links0
Images0
Faviconno

The quoted title and meta description are measurements of the other site. They are not this page's title or description.

Security

Family DNS for popyard.org is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.

Score breakdown

Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.

TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.

DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.

Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.

Domain age 5 of 5. Five points at one year, two points at 30 days.

Change history

First checked on 30 October 2026; changes will appear here.

Questions

Is popyard.org safe?

The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.

Who hosts popyard.org?

popyard.org is placed in Toronto, Canada.

When does popyard.org expire?

popyard.org expires on 11 July 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/popyard.org.

Who owns popyard.org?

The registry did not return a person or a company for popyard.org. RDAP often redacts the registrant. The registrar on file is Cloudflare, Inc..

Sources

  • RDAP source https://rdap.publicinterestregistry.org/rdap/domain/popyard.org at 2026-10-30T15:03:07Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:03:07Z
  • TLS source tls:443 at 2026-10-30T15:03:07Z
  • HTTP source https://popyard.org/ at 2026-10-30T15:03:07Z
  • Tech source wappalyzergo at 2026-10-30T15:03:07Z
  • Geo source db-ip at 2026-10-30T15:03:07Z
  • Safety source family DNS and local lists at 2026-10-30T15:03:07Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.org Cloudflare, Inc.

Owner of this site?

Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.

Removal policy

How to read this report

The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.