Domain report: norvig.com

Registration

info

.com generic · Network Solutions, LLC · expires 2035-12-31

Found

TLD: .com (generic)
ICANN policies apply: yes
Registrar: Network Solutions, LLC
Registered: 1 January 1997
Last changed: 2 October 2026
Expires: 31 December 2035
Status: client transfer prohibited
Registry nameservers: cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net, cp4.privatesystems.net
RDAP server: https://rdap.verisign.com/com/v1/

Checks

i

.com is a generic TLD (gTLD)

Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.

#1
✓ TLD delegated and signed #2

.com is delegated in the root zone and DNSSEC-signed.
✓ Expires on 2035-12-31 #3

The registration is valid until 2035-12-31 (3356 days).
✓ Transfer locked #4

Registry status: client transfer prohibited.
✓ Registry and delegation match #5

The nameservers registered at the registry are the ones published in DNS.

Delegation

info

cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net, cp4.privatesystems.net

Found

Parent zone: com
Delegation from: a.gtld-servers.net (192.5.6.30)
NS at the parent: cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net, cp4.privatesystems.net
NS in the zone: cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net, cp4.privatesystems.net

Nameserver	Addresses	Network (AS)	Glue
cp1.privatesystems.net	158.106.136.90 2600:4c00:80:11::1	AS63410 PRIVATESYSTEMS - PrivateSystems Networks, US AS63410 PRIVATESYSTEMS - PrivateSystems Networks, US	-
cp2.privatesystems.net	108.160.157.7 2600:4c00:509:731::a	AS63410 PRIVATESYSTEMS - PrivateSystems Networks, US AS63410 PRIVATESYSTEMS - PrivateSystems Networks, US	-
cp3.privatesystems.net	158.106.136.36 2600:4c00:80:9::1	AS63410 PRIVATESYSTEMS - PrivateSystems Networks, US AS63410 PRIVATESYSTEMS - PrivateSystems Networks, US	-
cp4.privatesystems.net	158.106.136.90 2600:4c00:80:11::1	AS63410 PRIVATESYSTEMS - PrivateSystems Networks, US AS63410 PRIVATESYSTEMS - PrivateSystems Networks, US	-

Checks

✓ 4 nameservers #6

Delegated to cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net, cp4.privatesystems.net.
✓ Parent and zone agree #7

The parent delegation and the zone's NS records list the same nameservers.
✓ No glue needed #8

All nameservers are outside the zone, so no glue records are needed.
✓ All names resolve #9

Every nameserver name has an address and is not an alias.
✓ Nameservers in different networks #10

The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS63410 (PRIVATESYSTEMS - PrivateSystems Networks, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

#11
i

All nameserver names under .net

All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.

#12
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
cp1.privatesystems.net 158.106.136.90	NOERROR, 102 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 14:13:28 by root@bh-centos-8.dev.cpanel.net)
cp1.privatesystems.net 2600:4c00:80:11::1	NOERROR, 99 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 14:13:28 by root@bh-centos-8.dev.cpanel.net)
cp2.privatesystems.net 108.160.157.7	NOERROR, 140 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)
cp2.privatesystems.net 2600:4c00:509:731::a	NOERROR, 140 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)
cp3.privatesystems.net 158.106.136.36	NOERROR, 103 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)
cp3.privatesystems.net 2600:4c00:80:9::1	NOERROR, 102 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)
cp4.privatesystems.net 158.106.136.90	NOERROR, 102 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 14:13:28 by root@bh-centos-8.dev.cpanel.net)
cp4.privatesystems.net 2600:4c00:80:11::1	NOERROR, 100 ms, authoritative	no	yes / yes	refused	PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 14:13:28 by root@bh-centos-8.dev.cpanel.net)

Checks

✓ All respond #14

All 8 nameserver addresses answered.
✓ All authoritative #15

Every responding nameserver answers authoritatively for the zone.
✓ No recursion #16

The nameservers do not answer recursive queries for other domains.
!

Software version disclosed

These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: cp1.privatesystems.net: "PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 14:13:28 by root@bh-centos-8.dev.cpanel.net)"; cp2.privatesystems.net: "PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)"; cp3.privatesystems.net: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)"; cp4.privatesystems.net: "PowerDNS Authoritative Server 4.9.17 (built Aug 10 2026 14:13:28 by root@bh-centos-8.dev.cpanel.net)". Hide or replace the version string.

#17
✓ Zone transfers refused #18

No nameserver allows a zone transfer to the public.
✓ TCP supported #19

All nameservers answer over TCP.
✓ EDNS supported #20

All nameservers support EDNS(0).
✓ Public addresses #21

All nameserver addresses are publicly routable.

SOA

pass

serial 2026100301 · primary cp1.privatesystems.net

Found

Primary (MNAME): cp1.privatesystems.net
Contact (RNAME): noc.privatesystems.net
Serial: 2026100301
Refresh / retry: 3600 s / 1800 s
Expire: 1209600 s
Negative TTL: 86400 s

Serial per nameserver

Nameserver	Serial
cp1.privatesystems.net (158.106.136.90)	2026100301
cp1.privatesystems.net (2600:4c00:80:11::1)	2026100301
cp2.privatesystems.net (108.160.157.7)	2026100301
cp2.privatesystems.net (2600:4c00:509:731::a)	2026100301
cp3.privatesystems.net (158.106.136.36)	2026100301
cp3.privatesystems.net (2600:4c00:80:9::1)	2026100301
cp4.privatesystems.net (158.106.136.90)	2026100301
cp4.privatesystems.net (2600:4c00:80:11::1)	2026100301

Checks

✓ Serial 2026100301 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 1h, retry 30m, expire 14d, negative TTL 1d.
✓ Primary is a public nameserver #24

The primary nameserver cp1.privatesystems.net is one of the listed nameservers.
✓ Contact noc@privatesystems.net #25

The SOA RNAME noc.privatesystems.net means noc@privatesystems.net.
✓ Date-based serial #26

The serial 2026100301 follows the YYYYMMDDnn convention (2026-10-03).

DNSSEC

warn

Not signed

Found

Validated by resolver: no

Checks

!

Not signed

The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

#27

Records

info

8 records at the apex

Found

Read from: 158.106.136.90:53

Type	Value	TTL
SOA	cp1.privatesystems.net. noc.privatesystems.net. 2026100301 3600 1800 1209600 86400	86400
NS	cp2.privatesystems.net.	86400
NS	cp3.privatesystems.net.	86400
NS	cp4.privatesystems.net.	86400
NS	cp1.privatesystems.net.	86400
A	158.106.138.13	14400
MX	0 norvig.com.	14400
TXT	"v=spf1 +mx +a +ip4:158.106.138.13 ~all"	14400

Checks

✓ TTLs within range #32

TTLs: A 4h, MX 4h, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
✓ No CNAME at the apex #33

The zone apex has no CNAME record.
✓ No wildcard #34

Names that don't exist return NXDOMAIN.
i

No CAA records

Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.

#35