anibookmark.com

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

HTTP 508SafeSSL: 39 days left10 years oldTranco #56015

One re-check per domain each UTC day.

55

anibookmark.com was registered on 13 Jun 2016 via GoDaddy.com, LLC and the registry expiry is 13 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/anibookmark.com.

anibookmark.com publishes 2 nameservers. DNSSEC is not signed.

anibookmark.com has 2 IPv4 addresses (104.21.73.252, 172.67.167.137) and 2 IPv6 addresses (2606:4700:3037::6815:49fc, 2606:4700:3037::ac43:a789). The geolocation database places 104.21.73.252 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 39 days left (TLS 1.3).

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

No safety warning was recorded for anibookmark.com in the checks that ran.

Domain · RDAP/WHOIS

anibookmark.com was registered on 13 Jun 2016 via GoDaddy.com, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/anibookmark.com.

Registeredsince 13 Jun 2016
Created13 June 2016
Updated15 June 2026
Expires13 June 2027
RegistrarGoDaddy.com, LLC
Statusactive
Nameserversdahlia.ns.cloudflare.com, oswald.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/anibookmark.com

Nameserver dahlia.ns.cloudflare.com is published for anibookmark.com in the registration record from https://rdap.verisign.com/com/v1/domain/anibookmark.com.

Nameserver oswald.ns.cloudflare.com is published for anibookmark.com in the registration record from https://rdap.verisign.com/com/v1/domain/anibookmark.com.

DNS

anibookmark.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.21.73.252, 172.67.167.137
AAAA2606:4700:3037::6815:49fc, 2606:4700:3037::ac43:a789
NSdahlia.ns.cloudflare.com, oswald.ns.cloudflare.com
MX—
SPFpresent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at anibookmark.com is "v=spf1 include:secureserver.net ~all".

IPv4 address 104.21.73.252 answers for anibookmark.com at resolver 1.1.1.1:53.

IPv4 address 172.67.167.137 answers for anibookmark.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3037::6815:49fc answers for anibookmark.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3037::ac43:a789 answers for anibookmark.com at resolver 1.1.1.1:53.

Hosting and geo

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

Address104.21.73.252
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for anibookmark.com is valid, with 39 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjectanibookmark.com
Valid from11 September 2026
Valid until10 December 2026
Days left39
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.anibookmark.com, anibookmark.com.

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 508 in 369 ms. The target title is 29 characters and the page has 1 H1 heading.

Status508
TTFB369 ms
Title length29 yes
Quoted title"508 Resource Limit Is Reached"
Meta descriptionnone no
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
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 anibookmark.com 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 10 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 anibookmark.com 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 anibookmark.com?

anibookmark.com is placed in Toronto, Canada.

When does anibookmark.com expire?

anibookmark.com expires on 13 June 2027 according to https://rdap.verisign.com/com/v1/domain/anibookmark.com.

Who owns anibookmark.com?

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

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/anibookmark.com at 2026-10-30T13:44:22Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:44:22Z
  • TLS source tls:443 at 2026-10-30T13:44:22Z
  • HTTP source https://anibookmark.com/ at 2026-10-30T13:44:22Z
  • Tech source wappalyzergo at 2026-10-30T13:44:22Z
  • Geo source db-ip at 2026-10-30T13:44:22Z
  • Safety source family DNS and local lists at 2026-10-30T13:44:22Z

Methodology

Related reports

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

.com 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.