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

0 in Queue, 1 of max. 8 Checks (20:18:04)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

X

 

DNS-problem - authoritative Nameserver refused, not defined or timeout

 

Checked:
14.02.2026 04:18:29

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
thesignal.com
A
198.12.17.231
North Mankato/Minnesota/United States (US) - Taylor Corporation
No Hostname found
yes
1
0

AAAA

yes


www.thesignal.com
CNAME
mwc-tm.trafficmanager.net
yes
1
0

A
198.12.17.231
North Mankato/Minnesota/United States (US) - Taylor Corporation
No Hostname found
yes


*.thesignal.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, 21:00:00 +, Signature-Inception: 13.02.2026, 20: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: thesignal.com

thesignal.com
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "oa5bdhk05s05bbeke0oi85ef6819g5if" between the hashed NSEC3-owner "oa5bcuvb061j64ottibrh4oti32djj5u" and the hashed NextOwner "oa5bupnnq5h0107jc8m4nvbol8dp88l7". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner oa5bcuvb061j64ottibrh4oti32djj5u.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 18.02.2026, 02:12:45 +, Signature-Inception: 11.02.2026, 01:02:45 +, KeyTag 35511, Signer-Name: com






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q3udg8cekkae7rukpgct1dvssh8ll". So that domain name is the Closest Encloser of "thesignal.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 19.02.2026, 00:27:10 +, Signature-Inception: 11.02.2026, 23:17:10 +, KeyTag 35511, Signer-Name: com






0 DNSKEY RR found









Zone: www.thesignal.com

www.thesignal.com
0 DS RR in the parent zone found



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: net

net
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=






1 RRSIG RR to validate DS RR found






RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.02.2026, 21:00:00 +, Signature-Inception: 13.02.2026, 20: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 37331, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 13, KeyTag 44109, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 21.02.2026, 15:10:35 +, Signature-Inception: 06.02.2026, 15:05:35 +, KeyTag 37331, Signer-Name: net






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






• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest "LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: trafficmanager.net

trafficmanager.net
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "cs4320kto8kf7vh8q5kagd3lpf228uql" between the hashed NSEC3-owner "cs42ooh5f7fgoeg6pc3ebjajfvgo0ktm" and the hashed NextOwner "cs43j8er2rvi7vcjp5ihj68hhme2q6gl". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner cs42ooh5f7fgoeg6pc3ebjajfvgo0ktm.net., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 19.02.2026, 03:28:27 +, Signature-Inception: 12.02.2026, 02:18:27 +, KeyTag 44109, Signer-Name: net






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "trafficmanager.net". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 19.02.2026, 03:31:38 +, Signature-Inception: 12.02.2026, 02:21:38 +, KeyTag 44109, Signer-Name: net






0 DNSKEY RR found









Zone: mwc-tm.trafficmanager.net

mwc-tm.trafficmanager.net
0 DS RR in the parent zone found






0 DNSKEY RR found







 

3. Name Servers

DomainNameserverNS-IP
thesignal.com
•  ns0054.secondary.cloudflare.com / 67m179
162.159.32.55
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
2606:4700:51::a29f:2037
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.		•

•  ns0209.secondary.cloudflare.com / 67m101
162.159.33.84
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

• 
2606:4700:59::a29f:2154
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.		•

•  ns5.assurant.com / 67m177
172.64.53.247
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•

•  ns6.assurant.com / 67m95
172.64.52.57
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.		•
com
•  a.gtld-servers.net / nnn1-par6
•

•  b.gtld-servers.net / nnn1-elwaw4
•

•  c.gtld-servers.net / nnn1-par6
•

•  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
•
mwc-tm.trafficmanager.net
•  tm1.dns-tm.com
150.171.10.240
Cleveland/Ohio/United States (US) - Microsoft Corporation		•

• 
2603:1061:0:f00::f0
Los Angeles/California/United States (US) - Microsoft Corporation		•
trafficmanager.net
•  tm1.dns-tm.com
150.171.10.240
Cleveland/Ohio/United States (US) - Microsoft Corporation		•

• 
2603:1061:0:f00::f0
Los Angeles/California/United States (US) - Microsoft Corporation		•

•  tm1.edgedns-tm.info
13.107.222.240
Québec/Canada (CA) - Microsoft Corporation		•

• 
2a01:111:4000:f00::f0
London/England/United Kingdom (GB) - MICROSOFT		•

•  tm2.dns-tm.com
150.171.16.240
Québec/Canada (CA) - Microsoft Corporation		•

• 
2620:1ec:8ec:f00::f0
Redmond/Washington/United States (US) - Microsoft Corporation		•

•  tm2.edgedns-tm.info
13.107.206.240
Toronto/Ontario/Canada (CA) - Microsoft Corporation		•

• 
2620:1ec:bda:f00::f0
Redmond/Washington/United States (US) - Microsoft Corporation		•
net
•  a.gtld-servers.net / nnn1-par6
•

•  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-ein3
•

•  l.gtld-servers.net / nnn1-frmrs-2
•

•  m.gtld-servers.net / nnn1-nlams-2e
•

 

4. SOA-Entries


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


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


Domain:thesignal.com
Zone-Name:thesignal.com
Primary:ns5.assurant.com
Mail:network.assurant.com
Serial:142
Refresh:10800
Retry:3600
Expire:1728000
TTL:900
num Entries:6


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


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


Domain:trafficmanager.net
Zone-Name:trafficmanager.net
Primary:tm1.dns-tm.com
Mail:hostmaster.trafficmanager.net
Serial:2003080800
Refresh:900
Retry:300
Expire:2419200
TTL:30
num Entries:8


Domain:mwc-tm.trafficmanager.net
Zone-Name:trafficmanager.net
Primary:tm1.dns-tm.com
Mail:hostmaster.trafficmanager.net
Serial:2003080800
Refresh:900
Retry:300
Expire:2419200
TTL:30
num Entries:2


5. Screenshots

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

 

 

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://thesignal.com/
198.12.17.231
-14


10.020
T
Timeout - The operation has timed out.

• http://www.thesignal.com/
198.12.17.231
-14


10.020
T
Timeout - The operation has timed out.

• https://thesignal.com/
198.12.17.231
-14


10.040
T
Timeout - The operation has timed out.

• https://www.thesignal.com/
198.12.17.231
-14


10.023
T
Timeout - The operation has timed out.

• http://thesignal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
198.12.17.231
-14


10.013
T
Timeout - The operation has timed out.
Visible Content:

• http://www.thesignal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
198.12.17.231
-14


10.030
T
Timeout - The operation has timed out.
Visible Content:

• https://198.12.17.231/
198.12.17.231
-14


10.030
T
Timeout - The operation has timed out.

 

7. Comments


1. General Results, most used to calculate the result

Aname "thesignal.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)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: thesignal.com has only one ip address.
Warning: Only one ip address found: www.thesignal.com has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: thesignal.com has no ipv6 address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.thesignal.com has no ipv6 address.
AGood: 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.
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 thesignal.com, 1 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.thesignal.com, 1 ip addresses.
BNo _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.thesignal.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

AInfo:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com, ns5.assurant.com, ns6.assurant.com, 2 Name Servers included in Delegation: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com, 2 Name Servers included in 1 Zone definitions: ns5.assurant.com, ns6.assurant.com, 1 Name Servers listed in SOA.Primary: ns5.assurant.com.
AGood: Only one SOA.Primary Name Server found.: ns5.assurant.com.
Error: SOA.Primary Name Server not included in the delegation set.: ns5.assurant.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns0054.secondary.cloudflare.com (162.159.32.55): Delegation: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com, Zone: ns5.assurant.com, ns6.assurant.com. Name Servers defined in Delegation, missing in Zone: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com.Name Servers defined in Zone, missing in Delegation: ns5.assurant.com, ns6.assurant.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns0054.secondary.cloudflare.com (2606:4700:51::a29f:2037): Delegation: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com, Zone: ns5.assurant.com, ns6.assurant.com. Name Servers defined in Delegation, missing in Zone: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com.Name Servers defined in Zone, missing in Delegation: ns5.assurant.com, ns6.assurant.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns0209.secondary.cloudflare.com (162.159.33.84): Delegation: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com, Zone: ns5.assurant.com, ns6.assurant.com. Name Servers defined in Delegation, missing in Zone: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com.Name Servers defined in Zone, missing in Delegation: ns5.assurant.com, ns6.assurant.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns0209.secondary.cloudflare.com (2606:4700:59::a29f:2154): Delegation: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com, Zone: ns5.assurant.com, ns6.assurant.com. Name Servers defined in Delegation, missing in Zone: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com.Name Servers defined in Zone, missing in Delegation: ns5.assurant.com, ns6.assurant.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns5.assurant.com (172.64.53.247): Delegation: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com, Zone: ns5.assurant.com, ns6.assurant.com. Name Servers defined in Delegation, missing in Zone: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com.Name Servers defined in Zone, missing in Delegation: ns5.assurant.com, ns6.assurant.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns6.assurant.com (172.64.52.57): Delegation: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com, Zone: ns5.assurant.com, ns6.assurant.com. Name Servers defined in Delegation, missing in Zone: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com.Name Servers defined in Zone, missing in Delegation: ns5.assurant.com, ns6.assurant.com.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
AGood: Some Name Servers have IPv6 addresses: 2 Name Servers with IPv6 found (2 Name Servers without IPv6)
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.: 4 Name Servers, 1 Top Level Domain: com
AGood: Name Servers with different domain names found.: 2 different Domains found
Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: CA
AInfo: Ipv4-Subnet-list: 4 Name Servers, 2 different subnets (first Byte): 162., 172., 2 different subnets (first two Bytes): 162.159., 172.64., 4 different subnets (first three Bytes): 162.159.32., 162.159.33., 172.64.52., 172.64.53.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2606:, 1 different subnets (first two blocks): 2606:4700:, 2 different subnets (first three blocks): 2606:4700:0051:, 2606:4700:0059:, 2 different subnets (first four blocks): 2606:4700:0051:0000:, 2606:4700:0059:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AInfo: Nameserver mit different domain names found. May be a problem with DNS-Updates
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
AGood: 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://thesignal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 198.12.17.231
-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.thesignal.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 198.12.17.231
-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.
AInfo: No img element found, no alt attribute checked
AGood: 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
ADuration: 225357 milliseconds, 225.357 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)

Issuerlast 7 daysactivenum Certs
CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
0
1
1
CN=Sectigo RSA Organization Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
13641446927
leaf cert		CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
2026-02-01 00:00:00
2026-05-02 23:59:59
thesignal.com - 1 entries


9755692169
leaf cert		CN=Sectigo RSA Organization Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2025-03-10 00:00:00
2026-03-10 23:59:59
assurantdeviceclaim.com, assurantdeviceclaims.com, clreviews.assurantsolutions.com, fastclaim.com, fastclaims.com, fastphones.com, myphpinfo.com, myphpinfopr.com, mytmoclaim.com, mywirelessclaim.com, mywirelessclaims.com, premiumcareclaim.com, premiumcareclaims.com, sppmobileclaims.com, thesignal.com, tmopdp.co, www.assurantdeviceclaim.com, www.assurantdeviceclaims.com, www.clreviews.assurantsolutions.com, www.fastclaim.com, www.fastclaims.com, www.fastphones.com, www.myphpinfo.com, www.myphpinfopr.com, www.mytmoclaim.com, www.mywirelessclaim.com, www.mywirelessclaims.com, www.premiumcareclaim.com, www.premiumcareclaims.com, www.sppmobileclaims.com, www.thesignal.com, www.tmopdp.co - 32 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: ns0054.secondary.cloudflare.com, ns0209.secondary.cloudflare.com, ns5.assurant.com, ns6.assurant.com

 

QNr.DomainTypeNS used
1
com
NS
a.root-servers.net (2001:503:ba3e::2:30)

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
ns0054.secondary.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
ns0209.secondary.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
ns5.assurant.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns0031.secondary.cloudflare.com, ns0156.secondary.cloudflare.com

Answer: ns0031.secondary.cloudflare.com
162.159.32.32, 2606:4700:51::a29f:2020

Answer: ns0156.secondary.cloudflare.com
162.159.33.31, 2606:4700:59::a29f:211f
5
ns6.assurant.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns0031.secondary.cloudflare.com, ns0156.secondary.cloudflare.com

Answer: ns0031.secondary.cloudflare.com
162.159.32.32, 2606:4700:51::a29f:2020

Answer: ns0156.secondary.cloudflare.com
162.159.33.31, 2606:4700:59::a29f:211f
6
ns0054.secondary.cloudflare.com: 162.159.32.55
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7
ns0054.secondary.cloudflare.com: 2606:4700:51::a29f:2037
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
8
ns0209.secondary.cloudflare.com: 162.159.33.84
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
9
ns0209.secondary.cloudflare.com: 2606:4700:59::a29f:2154
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
10
ns5.assurant.com: 172.64.53.247
A
ns0031.secondary.cloudflare.com (2606:4700:51::a29f:2020)
11
ns5.assurant.com: No AAAA record found
AAAA
ns0031.secondary.cloudflare.com (2606:4700:51::a29f:2020)
12
ns6.assurant.com: 172.64.52.57
A
ns0031.secondary.cloudflare.com (2606:4700:51::a29f:2020)
13
ns6.assurant.com: No AAAA record found
AAAA
ns0031.secondary.cloudflare.com (2606:4700:51::a29f:2020)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
mwc-tm.trafficmanager.net
0

no CAA entry found
1
0
trafficmanager.net
12
unknown
contactemailcaarecordaware@microsoft.com
1
0
www.thesignal.com



1
0
thesignal.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
thesignal.com
MS=ms79849234
ok
1
0
thesignal.com
v=spf1 mx ip4:167.79.177.0/24 ip4:167.79.190.0/27 ip4:167.79.14.192/29 include:spf.protection.outlook.com -all
ok
1
0
www.thesignal.com


1
0
mwc-tm.trafficmanager.net

ok
1
0
_acme-challenge.thesignal.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.thesignal.com

Name Error - The domain name does not exist
1
0
_acme-challenge.mwc-tm.trafficmanager.net

Name Error - The domain name does not exist
1
0
_acme-challenge.thesignal.com.thesignal.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.thesignal.com.thesignal.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.thesignal.com.www.thesignal.com

Name Error - The domain name does not exist
1
0
_acme-challenge.mwc-tm.trafficmanager.net.mwc-tm.trafficmanager.net

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

thesignal.com
10
atl0appcp002.assurant.com
04ok

A


167.79.177.82
01ok

CNAME


00ok
MX

thesignal.com
10
atl0appcp005.assurant.com
04ok

A


167.79.177.14
01ok

CNAME


00ok
MX

thesignal.com
10
ord3appcp001.assurant.com
04ok

A


167.79.14.192
01ok

CNAME


00ok
MX

thesignal.com
10
ord3appcp003.assurant.com
04ok

A


167.79.14.195
01ok

CNAME


00ok
SPF
TXT
thesignal.com

v=spf1 mx ip4:167.79.177.0/24 ip4:167.79.190.0/27 ip4:167.79.14.192/29 include:spf.protection.outlook.com -all
ok

MX
thesignal.com

atl0appcp002.assurant.com
ok

MX-A
atl0appcp002.assurant.com

167.79.177.82
ok

MX
thesignal.com

atl0appcp005.assurant.com
ok

MX-A
atl0appcp005.assurant.com

167.79.177.14
ok

MX
thesignal.com

ord3appcp001.assurant.com
ok

MX-A
ord3appcp001.assurant.com

167.79.14.192
8192Duplicated ipv4 found.

MX
thesignal.com

ord3appcp003.assurant.com
ok

MX-A
ord3appcp003.assurant.com

167.79.14.195
ok

TXT
thesignal.com

ip4:167.79.14.192/29
8192Duplicated ipv4 found.

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
_dmarc
TXT
_dmarc.thesignal.com

v=DMARC1;p=none;fo=1;rua=mailto:dmarc_rua@assurant.com;ruf=mailto:dmarc_ruf@assurant.com
ok

TXT
thesignal.com._report._dmarc.assurant.com

mailto:dmarc_rua@assurant.com
okMail domain unequal current domain. Check required, if there is a confirming _report._dmarc-Record. See RFC 7489, 7.1.

TXT
thesignal.com._report._dmarc.assurant.com

16Domainname not defined: NXDOMAIN. Report not sent.

TXT
thesignal.com._report._dmarc.assurant.com

mailto:dmarc_ruf@assurant.com
okMail domain unequal current domain. Check required, if there is a confirming _report._dmarc-Record. See RFC 7489, 7.1.

TXT
thesignal.com._report._dmarc.assurant.com

16Domainname not defined: NXDOMAIN. Report not sent.

				 
			

				 
			
17. Cipher Suites
No results 

				 
			
18. Portchecks



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



				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=56c45100-0909-476f-bec4-131338b3d4d6

				 
			


Last Result: https://check-your-website.server-daten.de/?q=thesignal.com - 2026-02-14 04:18:29

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

				 
			
<a href="https://check-your-website.server-daten.de/?q=thesignal.com" target="_blank">Check this Site: thesignal.com</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=thesignal.com

				 
			

				 
			



Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • 
USt-IdNr.: DE221734518

				 
			


Errors, ideas, questions? Use the 
Contact form • A project using

Server-Daten - Web Database solutions