bdstory.xyz

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

OfflineFamily DNS blockedUnder 1 year old

One re-check per domain each UTC day.

15

bdstory.xyz was registered on 13 Oct 2026 via GoDaddy.com, LLC and the registry expiry is 13 Oct 2027. WHOIS data came from RDAP at https://rdap.centralnic.com/xyz/domain/bdstory.xyz.

bdstory.xyz publishes 2 nameservers. DNSSEC is not signed.

bdstory.xyz has 1 IPv4 address (103.224.182.219). The geolocation database places 103.224.182.219 in San Diego, United States.

Domain · RDAP/WHOIS

bdstory.xyz was registered on 13 Oct 2026 via GoDaddy.com, LLC. The registry returned 5 status values and 2 nameservers from https://rdap.centralnic.com/xyz/domain/bdstory.xyz.

Registeredsince 13 Oct 2026
Created13 October 2026
Updated13 October 2026
Expires13 October 2027
RegistrarGoDaddy.com, LLC
Statusserver transfer prohibited, client renew prohibited, client transfer prohibited, client update prohibited, client delete prohibited
Nameserversns15.abovedomains.com, ns16.abovedomains.com
DNSSECno
Sourcehttps://rdap.centralnic.com/xyz/domain/bdstory.xyz

bdstory.xyz carries the status "server transfer prohibited". The registry itself is refusing transfers. The name stays at the current registrar while the status remains.

bdstory.xyz carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.

bdstory.xyz 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.

bdstory.xyz carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.

bdstory.xyz carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.

Nameserver ns15.abovedomains.com is published for bdstory.xyz in the registration record from https://rdap.centralnic.com/xyz/domain/bdstory.xyz.

Nameserver ns16.abovedomains.com is published for bdstory.xyz in the registration record from https://rdap.centralnic.com/xyz/domain/bdstory.xyz.

DNS

bdstory.xyz has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.

A103.224.182.219
AAAA—
NSns15.abovedomains.com, ns16.abovedomains.com
MXpark-mx.above.com (10)
SPFpresent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at bdstory.xyz is "v=spf1 ip6:fdcf:abda:4154::/48 -all".

IPv4 address 103.224.182.219 answers for bdstory.xyz at resolver 1.1.1.1:53.

Mail exchanger park-mx.above.com has preference 10.

A random label under bdstory.xyz also resolved, which means wildcard DNS is on.

Hosting and geo

bdstory.xyz is placed in San Diego, United States by the local geolocation database (db-ip).

Address103.224.182.219
CountryUnited States
CitySan Diego
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

No TLS certificate was read for bdstory.xyz on port 443.

Availableno
Sourcetls:443

dial tcp 103.224.182.219:443: i/o timeout

Tech stack

Tech detection did not run.

Checkedno
Sourcewappalyzergo

On-page checks

The homepage fetch did not return a status code.

Statusnone

context deadline exceeded

Security

Family DNS for bdstory.xyz is blocked, and URLhaus is clear. Source: family DNS and local lists.

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

Cloudflare family DNS returned a block for bdstory.xyz. That resolver covers adult and malware names.

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 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.

TLS 0 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 0 of 15. Points only when the checks ran and came back clean. Unknown is not clean.

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

Change history

  • October 2026: geo city changed from empty to San Diego.
  • October 2026: geo country changed from empty to United States.

Questions

Is bdstory.xyz safe?

Cloudflare family DNS returned a block for bdstory.xyz. That resolver covers adult and malware names.

Who hosts bdstory.xyz?

bdstory.xyz is placed in San Diego, United States.

When does bdstory.xyz expire?

bdstory.xyz expires on 13 October 2027 according to https://rdap.centralnic.com/xyz/domain/bdstory.xyz.

Who owns bdstory.xyz?

The registry did not return a person or a company for bdstory.xyz. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.

Sources

  • RDAP source https://rdap.centralnic.com/xyz/domain/bdstory.xyz at 2026-10-30T15:47:31Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:47:31Z
  • TLS source tls:443 at 2026-10-30T15:47:31Z
  • HTTP source https://bdstory.xyz/ at 2026-10-30T15:47:31Z
  • Tech source not available at 2026-10-30T15:47:31Z
  • Geo source db-ip at 2026-10-30T15:47:31Z
  • Safety source family DNS and local lists at 2026-10-30T15:47:31Z

Methodology

Related reports

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

.xyz GoDaddy.com, LLC

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.