hdfull.me

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

OfflineFamily DNS blockedSSL: 72 days left9 years old

One re-check per domain each UTC day.

25

hdfull.me was registered on 14 Sep 2017 via Dynadot Inc and the registry expiry is 14 Sep 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/hdfull.me.

hdfull.me publishes 2 nameservers. DNSSEC is not signed.

hdfull.me has 1 IPv4 address (162.4.84.239). The geolocation database places 162.4.84.239 in Los Angeles, United States.

The TLS certificate from YE1 is not valid (TLS 1.3).

Domain · RDAP/WHOIS

hdfull.me was registered on 14 Sep 2017 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/hdfull.me.

Registeredsince 14 Sep 2017
Created14 September 2017
Updated30 August 2026
Expires14 September 2027
RegistrarDynadot Inc
Statusclient transfer prohibited
Nameserversns1.ag614.parklogic.com, ns2.ag614.parklogic.com
DNSSECno
Sourcehttps://rdap.identitydigital.services/rdap/domain/hdfull.me

hdfull.me 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 ns1.ag614.parklogic.com is published for hdfull.me in the registration record from https://rdap.identitydigital.services/rdap/domain/hdfull.me.

Nameserver ns2.ag614.parklogic.com is published for hdfull.me in the registration record from https://rdap.identitydigital.services/rdap/domain/hdfull.me.

DNS

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

A162.4.84.239
AAAA—
NSns1.ag614.parklogic.com, ns2.ag614.parklogic.com
MXmx156.hostedmxserver.com (10)
SPFpresent
DMARCabsent
CAAissue letsencrypt.org
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at hdfull.me is "v=spf1 -all".

IPv4 address 162.4.84.239 answers for hdfull.me at resolver 1.1.1.1:53.

Mail exchanger mx156.hostedmxserver.com has preference 10.

A random label under hdfull.me also resolved, which means wildcard DNS is on.

A nameserver belongs to a parking host.

Hosting and geo

hdfull.me is placed in Los Angeles, United States by the local geolocation database (db-ip).

Address162.4.84.239
CountryUnited States
CityLos Angeles
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for hdfull.me is not valid, with 72 days left and 1 subject alternative name. Source: tls:443.

IssuerYE1
Subjecthdfull.me
Valid from13 October 2026
Valid until11 January 2027
Days left72
SAN count1
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: hdfull.me.

Validation result: certificate did not validate

Tech stack

Tech detection did not run.

Checkedno
Sourcewappalyzergo

On-page checks

The homepage fetch did not return a status code.

Statusnone

Get "https://hdfull.me/": tls: failed to verify certificate: x509: certificate signed by unknown authority

Security

Family DNS for hdfull.me 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 hdfull.me. 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 10 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 5 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: rdap created changed from 2017-09-14T20:49:27Z to 2017-09-14T20:49:27.197Z.
  • October 2026: rdap dnssec changed from unknown to no.
  • October 2026: rdap expires changed from 2027-09-14T20:49:27Z to 2027-09-14T20:49:27.197Z.
  • October 2026: rdap statuses changed from clienttransferprohibited to client transfer prohibited.
  • October 2026: rdap updated changed from 2026-08-30T10:02:27Z to 2026-08-30T10:02:27.609Z.
  • October 2026: geo city changed from empty to Los Angeles.
  • October 2026: geo country changed from empty to United States.

Questions

Is hdfull.me safe?

Cloudflare family DNS returned a block for hdfull.me. That resolver covers adult and malware names.

Who hosts hdfull.me?

hdfull.me is placed in Los Angeles, United States.

When does hdfull.me expire?

hdfull.me expires on 14 September 2027 according to https://rdap.identitydigital.services/rdap/domain/hdfull.me.

Who owns hdfull.me?

The registry did not return a person or a company for hdfull.me. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.

Sources

  • RDAP source https://rdap.identitydigital.services/rdap/domain/hdfull.me at 2026-10-30T14:44:03Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:44:03Z
  • TLS source tls:443 at 2026-10-30T14:44:03Z
  • HTTP source https://hdfull.me/ at 2026-10-30T14:44:03Z
  • Tech source not available at 2026-10-30T14:44:03Z
  • Geo source db-ip at 2026-10-30T14:44:03Z
  • Safety source family DNS and local lists at 2026-10-30T14:44:03Z

Methodology

Related reports

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

.me Dynadot 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.