bettnt.com

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

Online · 200SafeSSL: 88 days left15 years old

One re-check per domain each UTC day.

75

bettnt.com was registered on 1 Feb 2011 via NameSilo, LLC and the registry expiry is 1 Feb 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/bettnt.com.

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

bettnt.com has 2 IPv4 addresses (104.18.0.91, 104.18.1.91) and 2 IPv6 addresses (2606:4700::6812:15b, 2606:4700::6812:5b). The geolocation database places 104.18.0.91 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 88 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Cloudflare, HSTS and PHP. The fingerprints ran on the homepage that was already downloaded.

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

Domain · RDAP/WHOIS

bettnt.com was registered on 1 Feb 2011 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/bettnt.com.

Registeredsince 1 Feb 2011
Created1 February 2011
Updated27 March 2024
Expires1 February 2028
RegistrarNameSilo, LLC
Statusclient transfer prohibited
Nameserversalex.ns.cloudflare.com, lola.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/bettnt.com

bettnt.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 alex.ns.cloudflare.com is published for bettnt.com in the registration record from https://rdap.verisign.com/com/v1/domain/bettnt.com.

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

DNS

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

A104.18.0.91, 104.18.1.91
AAAA2606:4700::6812:15b, 2606:4700::6812:5b
NSalex.ns.cloudflare.com, lola.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 104.18.0.91 answers for bettnt.com at resolver 1.1.1.1:53.

IPv4 address 104.18.1.91 answers for bettnt.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700::6812:15b answers for bettnt.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700::6812:5b answers for bettnt.com at resolver 1.1.1.1:53.

Hosting and geo

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

Address104.18.0.91
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

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

IssuerWE1
Subjectbettnt.com
Valid from30 October 2026
Valid until28 January 2027
Days left88
SAN count2
ProtocolTLS 1.3
Sourcetls:443

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

Tech stack

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

  • Cloudflare · CDN
  • HSTS · Security
  • PHP · Programming languages

Cloudflare is filed under CDN.

HSTS is filed under Security.

PHP is filed under Programming languages.

On-page checks

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

Status200
TTFB0 ms
Title length0 no
Quoted titlenone
Meta descriptionnone no
H1 count0
HSTSyes yes
CSPno
X-Frame-OptionsSAMEORIGIN
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 bettnt.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
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 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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 10 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 bettnt.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 bettnt.com?

bettnt.com is placed in Toronto, Canada.

When does bettnt.com expire?

bettnt.com expires on 1 February 2028 according to https://rdap.verisign.com/com/v1/domain/bettnt.com.

Who owns bettnt.com?

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

Sources

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

Methodology

Related reports

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

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