AboutUs hasn't finished checking this site yet — the live checks below are current; more details appear as we crawl it.
Registered 2010 · site is live · HTTPS valid · on no blocklist we check
Got a different link you're not sure about? Check it or compare 009.xn--p1ai to another site.
Correct a description, link or other detail. Submissions are reviewed before publication.
009.xn--p1ai has an AboutUs profile for public website intelligence, ownership context, trust signals, monitoring, and owner verification.
Who has owned 009.xn--p1ai, and when it changed hands.
Registration eras, registrar and nameserver changes, certificate history, where on record — dated, with sources. An owner who stayed private shows as private.
Checked in the last 30 daysOlder, dated record
What AboutUs has on record for 009.xn--p1ai, by date.
No registration date on file yet. AboutUs reads it from RDAP when the site is checked.
AboutUs has no earlier page for 009.xn--p1ai; this record starts with the checks on this page.
No registrar observed yet. AboutUs has recorded registrars since Jul 20, 2026.
No registration-record history on file for this domain yet.
No .xn--p1ai zone-file record for 009.xn--p1ai is shown here yet.
Independent record by AboutUs · not written by 009.xn--p1ai
009.xn--p1ai
Authority
Not enough independent signals yet
Safety
Not enough signals yet
Measurements, not a verdict about the site. Authority scores draw on Open PageRank link-graph data.
How this is scoredDNS (passed)
HTTPS (passed)
Page metadata (passed)
Security headers (failed)
Add the HSTS, Content-Security-Policy, and X-Frame-Options response headers.
Latest available measurements; dated entries retain their dates. These are measurements, not an endorsement of the site.
Domain registered Nov 11, 2010 — 16 years old.
Registrar on record: REGRU-RF.
HTTPS request succeeded for 009.xn--p1ai.
Infrastructure record for 009.xn--p1ai
Powered by dns.pizzaRetrieved Nov 15, 2026, 4:01 PM UTC from dns.pizza. Individual measurements may be older.
Domain registration does not establish when the business was founded.
This describes the certificate observed at the measurement time for 009.xn--p1ai; it may have changed since.
Measures HTTP security-header hygiene (HSTS, Content-Security-Policy, and similar headers) — not whether the site is fraudulent or safe to use.
Trust record
How this is scored →Authority: not enough signals yetNot enough signals yet
We withhold an authority number until independent evidence (global rank, link-graph presence) has accrued. The facts we do have about this site are shown below — we'd rather say “not enough signals yet” than invent a low score.
Dated record — historical facts always carry their date.
Checked today — 3 of 4 safety checks passed (Nov 15, 2026).
People whose connection only uses the newer address style (IPv6) can't open 009.xn--p1ai and www.009.xn--p1ai directly. It works on the older style (IPv4), and visitors whose provider runs a translator still get through that way. This is a hosting setting, not a security problem, and it does not change the Safety score.
Ask whoever hosts your website
Ask them whether they can give your site a newer-style address. If they can, they will give you either an address to publish as an AAAA record, or a new name to point your domain at.
Option: put a service in front that has its own newer-connection address
Cloudflare turns this on by default, on every plan including the free one, for sites it proxies. To use it, your domain's DNS has to be managed at Cloudflare, with the record for your site set to "Proxied" (the orange cloud). This only works if your host allows a service in front of your site, so ask them first.
Source: Cloudflare documentation
Or leave it as it is
That is a reasonable choice. Visitors on the older kind of connection are not affected, and visitors whose provider runs a translator still get through that way.
Measured by aaaa.bot. See the measurement