boardreader.com

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

Online · 200SafeSSL: 188 days left25 years oldTranco #171536

One re-check per domain each UTC day.

90

boardreader.com was registered on 18 May 2001 via Squarespace Domains II LLC and the registry expiry is 18 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/boardreader.com.

boardreader.com publishes 4 nameservers. DNSSEC is not signed.

boardreader.com has 1 IPv4 address (208.92.218.68). The geolocation database places 208.92.218.68 in Troy, United States.

The TLS certificate from Sectigo Public Server Authentication CA DV R36 is valid and has 188 days left (TLS 1.2). The homepage answered HTTP 200.

Tech detection named Google Analytics, Google Tag Manager, HSTS and Nginx. The fingerprints ran on the homepage that was already downloaded.

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

Domain · RDAP/WHOIS

boardreader.com was registered on 18 May 2001 via Squarespace Domains II LLC. The registry returned 2 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/boardreader.com.

Registeredsince 18 May 2001
Created18 May 2001
Updated17 May 2024
Expires18 May 2027
RegistrarSquarespace Domains II LLC
Statusclient delete prohibited, client transfer prohibited
Nameserversns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/boardreader.com

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

boardreader.com 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 ns-cloud-d1.googledomains.com is published for boardreader.com in the registration record from https://rdap.verisign.com/com/v1/domain/boardreader.com.

Nameserver ns-cloud-d2.googledomains.com is published for boardreader.com in the registration record from https://rdap.verisign.com/com/v1/domain/boardreader.com.

Nameserver ns-cloud-d3.googledomains.com is published for boardreader.com in the registration record from https://rdap.verisign.com/com/v1/domain/boardreader.com.

Nameserver ns-cloud-d4.googledomains.com is published for boardreader.com in the registration record from https://rdap.verisign.com/com/v1/domain/boardreader.com.

DNS

boardreader.com has 1 address record, 5 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.

A208.92.218.68
AAAA—
NSns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com
MXaspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google
SPFpresent
DMARCpresent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at boardreader.com is "v=spf1 a ip4:54.72.19.249 ip4:208.92.218.188 ip4:208.92.218.162 ip4:208.92.218.66 include:_spf.google.com ~all".

The DMARC text record at _dmarc.boardreader.com is "v=DMARC1;p=none;sp=none;pct=100;adkim=r;aspf=r;rua=mailto:[email protected];ruf=mailto:[email protected];ri=86400;fo=1".

IPv4 address 208.92.218.68 answers for boardreader.com at resolver 1.1.1.1:53.

Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.

Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.

Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.

Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.

Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.

Hosting and geo

boardreader.com is placed in Troy, United States by the local geolocation database (db-ip).

Address208.92.218.68
CountryUnited States
CityTroy
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

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

IssuerSectigo Public Server Authentication CA DV R36
Subject*.boardreader.com
Valid from21 October 2026
Valid until7 May 2027
Days left188
SAN count2
ProtocolTLS 1.2
Sourcetls:443

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

Tech stack

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

  • Google Analytics · Analytics
  • Google Tag Manager · Tag managers
  • HSTS · Security
  • Nginx · Web servers, Reverse proxies

Google Analytics is filed under Analytics.

Google Tag Manager is filed under Tag managers.

HSTS is filed under Security.

Nginx is filed under Web servers, Reverse proxies.

On-page checks

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

Status200
TTFB229 ms
Title length33 yes
Quoted title"Boardreader - Forum Search Engine"
Meta descriptionnone no
H1 count0
HSTSyes yes
CSPyes
X-Frame-OptionsSAMEORIGIN
Robots metanoindex,nofollow
Canonical—
Language—
Links6
Images3
Faviconyes

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 boardreader.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
HSTSyes
CSPyes

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 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 15 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

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

Questions

Is boardreader.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 boardreader.com?

boardreader.com is placed in Troy, United States.

When does boardreader.com expire?

boardreader.com expires on 18 May 2027 according to https://rdap.verisign.com/com/v1/domain/boardreader.com.

Who owns boardreader.com?

The registry did not return a person or a company for boardreader.com. RDAP often redacts the registrant. The registrar on file is Squarespace Domains II LLC.

Sources

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

Methodology

Related reports

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

.com Squarespace Domains II 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.