Domain report: telecompaper.com

Registration

info

.com generic · Realtime Register B.V. · expires 2026-12-05

Found

TLD: .com (generic)
ICANN policies apply: yes
Registrar: Realtime Register B.V.
Registered: 5 December 2000
Last changed: 6 December 2025
Expires: 5 December 2026
Status: client transfer prohibited
Registry nameservers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
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 2026-12-05 #3

The registration is valid until 2026-12-05 (43 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

ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com

Found

Parent zone: com
Delegation from: a.gtld-servers.net (192.5.6.30)
NS at the parent: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
NS in the zone: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com

Nameserver	Addresses	Network (AS)	Glue
ns-cloud-b1.googledomains.com	216.239.32.107 2001:4860:4802:32::6b	AS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US	2001:4860:4802:32::6b 216.239.32.107
ns-cloud-b2.googledomains.com	216.239.34.107 2001:4860:4802:34::6b	AS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US	2001:4860:4802:34::6b 216.239.34.107
ns-cloud-b3.googledomains.com	216.239.36.107 2001:4860:4802:36::6b	AS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US	2001:4860:4802:36::6b 216.239.36.107
ns-cloud-b4.googledomains.com	216.239.38.107 2001:4860:4802:38::6b	AS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US	2001:4860:4802:38::6b 216.239.38.107

Checks

✓ 4 nameservers #6

Delegated to ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com.
✓ 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.
i

One address family in one network

all IPv6 addresses are in 2001:4860:4802::/48, while the other address family is spread over several networks.

#10
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS15169 (GOOGLE - Google LLC, 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 .com

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

pass

8 of 8 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns-cloud-b1.googledomains.com 216.239.32.107	NOERROR, 16 ms, authoritative	no	yes / yes	refused	-
ns-cloud-b1.googledomains.com 2001:4860:4802:32::6b	NOERROR, 16 ms, authoritative	no	yes / yes	refused	-
ns-cloud-b2.googledomains.com 216.239.34.107	NOERROR, 14 ms, authoritative	no	yes / yes	refused	-
ns-cloud-b2.googledomains.com 2001:4860:4802:34::6b	NOERROR, 17 ms, authoritative	no	yes / yes	refused	-
ns-cloud-b3.googledomains.com 216.239.36.107	NOERROR, 46 ms, authoritative	no	yes / yes	refused	-
ns-cloud-b3.googledomains.com 2001:4860:4802:36::6b	NOERROR, 46 ms, authoritative	no	yes / yes	refused	-
ns-cloud-b4.googledomains.com 216.239.38.107	NOERROR, 12 ms, authoritative	no	yes / yes	refused	-
ns-cloud-b4.googledomains.com 2001:4860:4802:38::6b	NOERROR, 11 ms, authoritative	no	yes / yes	refused	-

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.
✓ No version disclosed #17

The nameservers don't reveal their software version.
✓ 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

warn

serial 1 · primary ns-cloud-b1.googledomains.com

Found

Primary (MNAME): ns-cloud-b1.googledomains.com
Contact (RNAME): cloud-dns-hostmaster.google.com
Serial: 1
Refresh / retry: 21600 s / 3600 s
Expire: 259200 s
Negative TTL: 300 s

Serial per nameserver

Nameserver	Serial
ns-cloud-b1.googledomains.com (216.239.32.107)	1
ns-cloud-b1.googledomains.com (2001:4860:4802:32::6b)	1
ns-cloud-b2.googledomains.com (216.239.34.107)	1
ns-cloud-b2.googledomains.com (2001:4860:4802:34::6b)	1
ns-cloud-b3.googledomains.com (216.239.36.107)	1
ns-cloud-b3.googledomains.com (2001:4860:4802:36::6b)	1
ns-cloud-b4.googledomains.com (216.239.38.107)	1
ns-cloud-b4.googledomains.com (2001:4860:4802:38::6b)	1

Checks

✓ Serial 1 everywhere #22

All nameservers serve the same version of the zone.
!

Unusual SOA timers

expire 3d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 6h, retry 1h, expire 3d, negative TTL 5m.

#23
✓ Primary is a public nameserver #24

The primary nameserver ns-cloud-b1.googledomains.com is one of the listed nameservers.
✓ Contact cloud-dns-hostmaster@google.com #25

The SOA RNAME cloud-dns-hostmaster.google.com means cloud-dns-hostmaster@google.com.
✓ Counter serial #26

The serial 1 is a plain counter.

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver: no
Denial of existence: NSEC3
NSEC3: 1 iterations, 8-byte salt
Signatures valid until: 11 November 2026

DNSKEY in the zone

Key tag	Role	Algorithm
21058	ZSK (256)	RSASHA256 (8)
17990	KSK (257)	RSASHA256 (8)

Checks

!

Signed but not delegated securely

The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.

#27
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
✓ Signatures valid until 2026-11-11 #30

The earliest DNSKEY/SOA signature expires at 2026-11-11 20:20 UTC.
!

NSEC3 with extra iterations or salt

NSEC3 uses 1 iteration and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.

#31

Records

info

15 records at the apex

Found

Read from: 216.239.32.107:53

Type	Value	TTL
SOA	ns-cloud-b1.googledomains.com. cloud-dns-hostmaster.google.com. 1 21600 3600 259200 300	21600
NS	ns-cloud-b2.googledomains.com.	21600
NS	ns-cloud-b1.googledomains.com.	21600
NS	ns-cloud-b3.googledomains.com.	21600
NS	ns-cloud-b4.googledomains.com.	21600
A	34.149.23.30	300
MX	10 telecompaper-com.mail.protection.outlook.com.	600
TXT	"google-site-verification=kq_hHm3o2dhAUIHweb3xgmuva8_DxrmsBbCy7SxRd1g"	120
TXT	"MS=ms12137656"	120
TXT	"nyrcpwdqpvsmzmkwmv6p9tzf30xv2cmb"	120
TXT	"knowbe4-site-verification=dc058931e27cc3a4c17e1d5c6b2a5926"	120
TXT	"v=spf1 mx a include:de._netblocks.mimecast.com ip4:5.79.70.90 ip4:84.35.104.92 ip4:83.167.206.147 ip4:37.48.69.133 include:spf.protection.outlook.com ip4:194.165.34.0/24 include:spf.mandrillapp.com -all"	120
TXT	"google-site-verification=SvhSYShwaxwo7Iod1JwmoCtLQ8rsOsym-ENAdD0ayDc"	120
TXT	"MS=ms24609572"	120
TXT	"0ed1fe018ae3be49de387c471d93ffcc4e3b16feb1"	120

Checks

✓ TTLs within range #32

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

The zone apex has no CNAME record.
i

Wildcard record

A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.

#34
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