Check DNS, Urls + Redirects, Certificates and Content of your Website

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
13.02.2026 09:17:19

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
tgmcc.com	A	104.21.94.102 Toronto/Ontario/Canada (CA) - Cloudflare, Inc. No Hostname found	yes	1	0
	A	172.67.222.89 Toronto/Ontario/Canada (CA) - Cloudflare, Inc. No Hostname found	yes	1	0
	AAAA	2606:4700:3034::ac43:de59 Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	yes
	AAAA	2606:4700:3037::6815:5e66 Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	yes
www.tgmcc.com	A	104.21.94.102 Toronto/Ontario/Canada (CA) - Cloudflare, Inc. No Hostname found	yes	1	0
	A	172.67.222.89 Toronto/Ontario/Canada (CA) - Cloudflare, Inc. No Hostname found	yes	1	0
	AAAA	2606:4700:3034::ac43:de59 Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	yes
	AAAA	2606:4700:3037::6815:5e66 Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	yes
*.tgmcc.com	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes

2. DNSSEC

Zone (*)	DNSSEC - Informations

Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 21831, Flags 256


	Public Key with Algorithm 8, KeyTag 38696, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 03.03.2026, 00:00:00 +, Signature-Inception: 10.02.2026, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: com
com	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.02.2026, 05:00:00 +, Signature-Inception: 13.02.2026, 04:00:00 +, KeyTag 21831, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 21831 used to validate the DS RRSet in the parent zone


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 19718, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 35511, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 21.02.2026, 15:02:35 +, Signature-Inception: 06.02.2026, 14:57:35 +, KeyTag 19718, Signer-Name: com


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 19718 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest "isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: tgmcc.com
tgmcc.com	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 2371, DigestType 2 and Digest Dx8avAnr4dqE2bf9HIFndyXS2KGB953mov2GIrEOfTk=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner tgmcc.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 19.02.2026, 01:25:13 +, Signature-Inception: 12.02.2026, 00:15:13 +, KeyTag 35511, Signer-Name: com


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 35511 used to validate the DS RRSet in the parent zone


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 2371, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 34505, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner tgmcc.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 24.03.2026, 06:55:42 +, Signature-Inception: 22.01.2026, 06:55:42 +, KeyTag 2371, Signer-Name: tgmcc.com


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 2371 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 2371, DigestType 2 and Digest "Dx8avAnr4dqE2bf9HIFndyXS2KGB953mov2GIrEOfTk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone


	RRSIG Type 1 validates the A - Result: 104.21.94.102 172.67.222.89 Validated: RRSIG-Owner tgmcc.com., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	RRSIG Type 16 validates the TXT - Result: v=spf1 include:spf.protection.outlook.com -all google-gws-recovery-domain-verification=60103841 openai-domain-verification=dv-A90JMV66FPbD96IoXdEOrQyq google-site-verification=yZGtfqPRvNRoEnj_Mv7Halj43m7_i3KN11bCHvCtE3E Validated: RRSIG-Owner tgmcc.com., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	RRSIG Type 28 validates the AAAA - Result: 2606:4700:3034:0000:0000:0000:AC43:DE59 2606:4700:3037:0000:0000:0000:6815:5E66 Validated: RRSIG-Owner tgmcc.com., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	CNAME-Query sends a valid NSEC RR as result with the query name "tgmcc.com" equal the NSEC-owner "tgmcc.com" and the NextOwner "\000.tgmcc.com". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, URI, CAA Validated: RRSIG-Owner tgmcc.com., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.tgmcc.com) sends a valid NSEC RR as result with the query name "_443._tcp.tgmcc.com" equal the NSEC-owner "_443._tcp.tgmcc.com" and the NextOwner "\000._443._tcp.tgmcc.com". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: RRSIG, NSEC, 128 Validated: RRSIG-Owner _443._tcp.tgmcc.com., Algorithm: 13, 4 Labels, original TTL: 1800 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "tgmcc.com" equal the NSEC-owner "tgmcc.com" and the NextOwner "\000.tgmcc.com". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, URI Validated: RRSIG-Owner tgmcc.com., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	Status: Good. NoData-Proof required and found.

Zone: www.tgmcc.com
www.tgmcc.com	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "www.tgmcc.com" and the NextOwner "\000.www.tgmcc.com". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA


	RRSIG Type 1 validates the A - Result: 104.21.94.102 172.67.222.89 Validated: RRSIG-Owner www.tgmcc.com., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	RRSIG Type 28 validates the AAAA - Result: 2606:4700:3034:0000:0000:0000:AC43:DE59 2606:4700:3037:0000:0000:0000:6815:5E66 Validated: RRSIG-Owner www.tgmcc.com., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	CNAME-Query sends a valid NSEC RR as result with the query name "www.tgmcc.com" equal the NSEC-owner "www.tgmcc.com" and the NextOwner "\000.www.tgmcc.com". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA Validated: RRSIG-Owner www.tgmcc.com., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "www.tgmcc.com" equal the NSEC-owner "www.tgmcc.com" and the NextOwner "\000.www.tgmcc.com". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, 13, MX, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA Validated: RRSIG-Owner www.tgmcc.com., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.www.tgmcc.com) sends a valid NSEC RR as result with the query name "_443._tcp.www.tgmcc.com" equal the NSEC-owner "_443._tcp.www.tgmcc.com" and the NextOwner "\000._443._tcp.www.tgmcc.com". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: RRSIG, NSEC, 128 Validated: RRSIG-Owner _443._tcp.www.tgmcc.com., Algorithm: 13, 5 Labels, original TTL: 1800 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "www.tgmcc.com" equal the NSEC-owner "www.tgmcc.com" and the NextOwner "\000.www.tgmcc.com". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI Validated: RRSIG-Owner www.tgmcc.com., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 14.02.2026, 09:17:37 +, Signature-Inception: 12.02.2026, 07:17:37 +, KeyTag 34505, Signer-Name: tgmcc.com


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
www.tgmcc.com	• ian.ns.cloudflare.com / 67m67		•
tgmcc.com	• ian.ns.cloudflare.com / 67m163	108.162.193.118 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	172.64.33.118 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	173.245.59.118 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2606:4700:58::adf5:3b76 Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	•
	•	2803:f800:50::6ca2:c176 San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.	•
	•	2a06:98c1:50::ac40:2176 London/England/United Kingdom (GB) - CloudFLARENET-EU	•
	• pam.ns.cloudflare.com / 67m160	108.162.192.138 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	172.64.32.138 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	173.245.58.138 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2606:4700:50::adf5:3a8a Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	•
	•	2803:f800:50::6ca2:c08a San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.	•
	•	2a06:98c1:50::ac40:208a London/England/United Kingdom (GB) - CloudFLARENET-EU	•
com	• a.gtld-servers.net / nnn1-defra-5		•
	• b.gtld-servers.net / nnn1-elwaw4		•
	• c.gtld-servers.net / nnn1-defra-5		•
	• d.gtld-servers.net / nnn1-par6		•
	• e.gtld-servers.net / nnn1-par6		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-frmrs-2		•
	• k.gtld-servers.net / nnn1-frmrs-2		•
	• l.gtld-servers.net / nnn1-frmrs-2		•
	• m.gtld-servers.net / nnn1-frmrs-2		•

4. SOA-Entries

Domain:	com
Zone-Name:	com
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1770970625
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	12

Domain:	com
Zone-Name:	com
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1770970640
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	1

Domain:	tgmcc.com
Zone-Name:	tgmcc.com
Primary:	ian.ns.cloudflare.com
Mail:	dns.cloudflare.com
Serial:	2395796744
Refresh:	10000
Retry:	2400
Expire:	604800
TTL:	1800
num Entries:	12

Domain:	www.tgmcc.com
Zone-Name:	tgmcc.com
Primary:	ian.ns.cloudflare.com
Mail:	dns.cloudflare.com
Serial:	2395796744
Refresh:	10000
Retry:	2400
Expire:	604800
TTL:	1800
num Entries:	1

5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

Domainname	Http-Status	Sec.	G
• http://tgmcc.com:5001/ 104.21.94.102	-14	10.020	T
Timeout - The operation has timed out.

• http://tgmcc.com:5001/ 172.67.222.89	-14	10.020	T
Timeout - The operation has timed out.

• http://tgmcc.com:5001/ 2606:4700:3034::ac43:de59	-14	10.013	T
Timeout - The operation has timed out.

• http://tgmcc.com:5001/ 2606:4700:3037::6815:5e66	-14	10.017	T
Timeout - The operation has timed out.

• http://www.tgmcc.com:5001/ 104.21.94.102	-14	10.027	T
Timeout - The operation has timed out.

• http://www.tgmcc.com:5001/ 172.67.222.89	-14	10.023	T
Timeout - The operation has timed out.

• http://www.tgmcc.com:5001/ 2606:4700:3034::ac43:de59	-14	10.023	T
Timeout - The operation has timed out.

• http://www.tgmcc.com:5001/ 2606:4700:3037::6815:5e66	-14	10.020	T
Timeout - The operation has timed out.

• https://tgmcc.com:5001/ 104.21.94.102	-14	10.020	T
Timeout - The operation has timed out.

• https://tgmcc.com:5001/ 172.67.222.89	-14	10.013	T
Timeout - The operation has timed out.

• https://tgmcc.com:5001/ 2606:4700:3034::ac43:de59	-14	10.024	T
Timeout - The operation has timed out.

• https://tgmcc.com:5001/ 2606:4700:3037::6815:5e66	-14	10.023	T
Timeout - The operation has timed out.

• https://www.tgmcc.com:5001/ 104.21.94.102	-14	10.020	T
Timeout - The operation has timed out.

• https://www.tgmcc.com:5001/ 172.67.222.89	-14	10.024	T
Timeout - The operation has timed out.

• https://www.tgmcc.com:5001/ 2606:4700:3034::ac43:de59	-14	10.023	T
Timeout - The operation has timed out.

• https://www.tgmcc.com:5001/ 2606:4700:3037::6815:5e66	-14	10.023	T
Timeout - The operation has timed out.

• http://tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.94.102	-14	10.020	T
Timeout - The operation has timed out.
Visible Content:

• http://tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.222.89	-14	10.020	T
Timeout - The operation has timed out.
Visible Content:

• http://tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3034::ac43:de59	-14	10.014	T
Timeout - The operation has timed out.
Visible Content:

• http://tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3037::6815:5e66	-14	10.020	T
Timeout - The operation has timed out.
Visible Content:

• http://www.tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.94.102	-14	10.020	T
Timeout - The operation has timed out.
Visible Content:

• http://www.tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.222.89	-14	10.020	T
Timeout - The operation has timed out.
Visible Content:

• http://www.tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3034::ac43:de59	-14	10.027	T
Timeout - The operation has timed out.
Visible Content:

• http://www.tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3037::6815:5e66	-14	10.016	T
Timeout - The operation has timed out.
Visible Content:

• https://104.21.94.102:5001/ 104.21.94.102	-14	10.017	T
Timeout - The operation has timed out.

• https://172.67.222.89:5001/ 172.67.222.89	-14	10.017	T
Timeout - The operation has timed out.

• https://[2606:4700:3034:0000:0000:0000:ac43:de59]:5001/ 2606:4700:3034::ac43:de59	-14	10.027	T
Timeout - The operation has timed out.

• https://[2606:4700:3037:0000:0000:0000:6815:5e66]:5001/ 2606:4700:3037::6815:5e66	-14	10.027	T
Timeout - The operation has timed out.

7. Comments

	1. General Results, most used to calculate the result
A	name "tgmcc.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 108094 (complete: 276475)
A	Good: All ip addresses are public addresses
A	Good: Minimal 2 ip addresses per domain name found: tgmcc.com has 4 different ip addresses (authoritative).
A	Good: Minimal 2 ip addresses per domain name found: www.tgmcc.com has 4 different ip addresses (authoritative).
A	Good: Ipv4 and Ipv6 addresses per domain name found: tgmcc.com has 2 ipv4, 2 ipv6 addresses
A	Good: Ipv4 and Ipv6 addresses per domain name found: www.tgmcc.com has 2 ipv4, 2 ipv6 addresses
A	Good: No asked Authoritative Name Server had a timeout
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
A	Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain tgmcc.com, 4 ip addresses.
A	Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.tgmcc.com, 4 ip addresses.
	Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain tgmcc.com, 4 ip addresses.
	Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.tgmcc.com, 4 ip addresses.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.tgmcc.com
	2. Header-Checks
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: ian.ns.cloudflare.com, pam.ns.cloudflare.com, 2 Name Servers included in Delegation: ian.ns.cloudflare.com, pam.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: ian.ns.cloudflare.com, pam.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: ian.ns.cloudflare.com.
A	Good: Only one SOA.Primary Name Server found.: ian.ns.cloudflare.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ian.ns.cloudflare.com.
A	Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ian.ns.cloudflare.com, pam.ns.cloudflare.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
	Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com
	Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: cloudflare.com
A	Good: Name servers with different Country locations found: 2 Name Servers, 3 Countries: CA, CR, GB
A	Info: Ipv4-Subnet-list: 6 Name Servers, 3 different subnets (first Byte): 108., 172., 173., 3 different subnets (first two Bytes): 108.162., 172.64., 173.245., 6 different subnets (first three Bytes): 108.162.192., 108.162.193., 172.64.32., 172.64.33., 173.245.58., 173.245.59.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2606:, 2803:, 2a06:, 3 different subnets (first two blocks): 2606:4700:, 2803:f800:, 2a06:98c1:, 4 different subnets (first three blocks): 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 4 different subnets (first four blocks): 2606:4700:0050:0000:, 2606:4700:0058:0000:, 2803:f800:0050:0000:, 2a06:98c1:0050:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 12 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 12 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver
A	Good: All SOA have the same Serial Number
	Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
	4. Content- and Performance-critical Checks
	http://tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.94.102	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.222.89	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3034::ac43:de59	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3037::6815:5e66	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.21.94.102	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 172.67.222.89	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3034::ac43:de59	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.tgmcc.com:5001/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700:3037::6815:5e66	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Info: No img element found, no alt attribute checked
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
A	Duration: 339044 milliseconds, 339.044 seconds

8. Connections

No connection informations found. Perhaps only http - connections.

9. Certificates

No certificate informations found. Perhaps only http - connections.

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuer				last 7 days	active	num Certs
CN=Sectigo Public Server Authentication CA DV E36, O=Sectigo Limited, C=GB				0	2	2
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2				0	1	1
CN=WE1, O=Google Trust Services, C=US				0	1	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
13402591968 precert	//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2	2026-01-11 14:22:28	2026-04-11 14:22:28	tgmcc.com, www.tgmcc.com - 2 entries
13111727555 leaf cert	CN=WE1, O=Google Trust Services, C=US	2025-12-17 07:52:13	2026-03-17 08:48:19	*.tgmcc.com, tgmcc.com - 2 entries
13111834788 leaf cert	CN=Sectigo Public Server Authentication CA DV E36, O=Sectigo Limited, C=GB	2025-12-17 00:00:00	2026-03-17 08:58:49	*.tgmcc.com, tgmcc.com - 2 entries
13111927036 leaf cert	CN=Sectigo Public Server Authentication CA DV E36, O=Sectigo Limited, C=GB	2025-12-17 00:00:00	2026-03-17 09:02:44	*.tgmcc.com, tgmcc.com - 2 entries

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

No CRT - CT-Log entries found

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

12. Html-Parsing via https://validator.w3.org/nu/

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ian.ns.cloudflare.com, pam.ns.cloudflare.com

QNr.	Domain	Type	NS used
1	com	NS	f.root-servers.net (2001:500:2f::f)
	Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2	ian.ns.cloudflare.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
	Answer: ns3.cloudflare.com 162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2
	Answer: ns4.cloudflare.com 162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837
	Answer: ns5.cloudflare.com 162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937
	Answer: ns6.cloudflare.com 162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506
	Answer: ns7.cloudflare.com 162.159.4.8, 162.159.6.6, 2400:cb00:2049:1::a29f:408, 2400:cb00:2049:1::a29f:606
3	pam.ns.cloudflare.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
	Answer: ns3.cloudflare.com 162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2
	Answer: ns4.cloudflare.com 162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837
	Answer: ns5.cloudflare.com 162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937
	Answer: ns6.cloudflare.com 162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506
	Answer: ns7.cloudflare.com 162.159.4.8, 162.159.6.6, 2400:cb00:2049:1::a29f:408, 2400:cb00:2049:1::a29f:606
4	ian.ns.cloudflare.com: 108.162.193.118, 172.64.33.118, 173.245.59.118	A	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
5	ian.ns.cloudflare.com: 2606:4700:58::adf5:3b76, 2803:f800:50::6ca2:c176, 2a06:98c1:50::ac40:2176	AAAA	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
6	pam.ns.cloudflare.com: 108.162.192.138, 172.64.32.138, 173.245.58.138	A	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7	pam.ns.cloudflare.com: 2606:4700:50::adf5:3a8a, 2803:f800:50::6ca2:c08a, 2a06:98c1:50::ac40:208a	AAAA	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)

14. CAA - Entries

Domainname	Value	∑ Queries
www.tgmcc.com	no CAA entry found	1
tgmcc.com	no CAA entry found	1
com	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
tgmcc.com	google-gws-recovery-domain-verification=60103841	ok	1
tgmcc.com	google-site-verification=yZGtfqPRvNRoEnj_Mv7Halj43m7_i3KN11bCHvCtE3E	ok	1
tgmcc.com	openai-domain-verification=dv-A90JMV66FPbD96IoXdEOrQyq	ok	1
tgmcc.com	v=spf1 include:spf.protection.outlook.com -all	ok	1
www.tgmcc.com		ok	1
_acme-challenge.tgmcc.com		Name Error - The domain name does not exist	1
_acme-challenge.www.tgmcc.com		Name Error - The domain name does not exist	1
_acme-challenge.tgmcc.com.tgmcc.com		Name Error - The domain name does not exist	1
_acme-challenge.www.tgmcc.com.tgmcc.com		Name Error - The domain name does not exist	1
_acme-challenge.www.tgmcc.com.www.tgmcc.com		Name Error - The domain name does not exist	1

16. DomainService - Entries

Type		Domain	Pref	Value	DNS-error	num Answers	Status
MX		tgmcc.com	0	tgmcc-com.mail.protection.outlook.com	0	1	ok
	A			52.101.194.0	0	4	ok
	A			52.101.42.14	0	4	ok
	A			52.101.50.7	0	4	ok
	A			52.101.41.56	0	4	ok
	AAAA			2a01:111:f403:f901::2	0	4	ok
	AAAA			2a01:111:f403:c901::1	0	4	ok
	AAAA			2a01:111:f403:c927::1	0	4	ok
	AAAA			2a01:111:f403:f802::1	0	4	ok
	CNAME				-4	0	ok
SPF	TXT	tgmcc.com		v=spf1 include:spf.protection.outlook.com -all			ok
	TXT	spf.protection.outlook.com		v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all			ok

17. Cipher Suites

Skipped, CDN used or too many ip addresses

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=04a8f351-a348-4064-8f15-660b4106355e

Last Result: https://check-your-website.server-daten.de/?q=tgmcc.com%3A5001 - 2026-02-13 09:17:19

Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=tgmcc.com%3A5001" target="_blank">Check this Site: tgmcc.com%3A5001</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

QR-Code of this page - https://check-your-website.server-daten.de/?d=tgmcc.com:5001