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

...

skip EDNS-Check

skip Content-Check

check links

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

Checked:
02.08.2023 00:00:09

Older results

X - 24.11.2022 02:20:05

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
chatremix.com	A	82.28.202.151 Leeds/England/United Kingdom (GB) - Virgin Media Limited Hostname: cpc91558-seac25-2-0-cust662.7-2.cable.virginm.net	yes	1	0
	AAAA		yes
www.chatremix.com	A	82.28.202.151 Leeds/England/United Kingdom (GB) - Virgin Media Limited Hostname: cpc91558-seac25-2-0-cust662.7-2.cable.virginm.net	yes	1	0
	AAAA		yes
*.chatremix.com	A	82.28.202.151	yes
	AAAA		yes
	CNAME		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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 11019, Flags 256


	Public Key with Algorithm 8, KeyTag 20326, 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: 21.08.2023, 00:00:00 +, Signature-Inception: 31.07.2023, 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 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.08.2023, 17:00:00 +, Signature-Inception: 01.08.2023, 16:00:00 +, KeyTag 11019, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 4459, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 13.08.2023, 17:24:21 +, Signature-Inception: 29.07.2023, 17:19:21 +, KeyTag 30909, Signer-Name: com


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


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

Zone: chatremix.com
chatremix.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 "foc2oo8nqshuoi8qp4rb26ign852qjti" between the hashed NSEC3-owner "foc2mr5buj1amvc5t37mublcerdumfah" and the hashed NextOwner "foc2t87191am9v289uv4av1c4ks0ods5". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner foc2mr5buj1amvc5t37mublcerdumfah.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 08.08.2023, 05:36:37 +, Signature-Inception: 01.08.2023, 04:26:37 +, KeyTag 4459, 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 "ck0q2d6ni4i7eqh8na30ns61o48ul8g5". So that domain name is the Closest Encloser of "chatremix.com". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 06.08.2023, 04:24:23 +, Signature-Inception: 30.07.2023, 03:14:23 +, KeyTag 4459, Signer-Name: com


	0 DNSKEY RR found




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

3. Name Servers

Domain	Nameserver	NS-IP
www.chatremix.com	• ns2.no-ip.com
chatremix.com	• ns1.no-ip.com / P0201-CDG-HV	194.62.181.53 London/England/United Kingdom (GB) - ARTEC	•
	•	2a07:dc00:1810::53 Amsterdam/North Holland/Netherlands (NL) - Vitalwerks Internet Solutions, LLC	•
	• ns2.no-ip.com / P0201-CDG-VR	194.62.180.53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:180::53 Amsterdam/North Holland/Netherlands (NL) - Vitalwerks Internet Solutions, LLC	•
	• ns3.no-ip.com / P0202-FRA-HV	204.16.255.53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:2550::53 Amsterdam/North Holland/Netherlands (NL) - Vitalwerks Internet Solutions, LLC	•
	• ns4.no-ip.com / h0301.fra.eq.as29997.net	204.16.254.53 New York/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2620:0:2e64::53 Secaucus/New Jersey/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• ns5.no-ip.com / P0201-CDG-HV	194.62.181.53 London/England/United Kingdom (GB) - ARTEC	•
	• static-1.no-ip.com / P0201-CDG-HV	194.62.181.53 London/England/United Kingdom (GB) - ARTEC	•
	• static-2.no-ip.com / s0202	45.77.3.172 Santa Clara/California/United States (US) - The Constant Company	•
	• static-3.no-ip.com / s0203	104.207.132.142 Piscataway/New Jersey/United States (US) - Choopa	•
com	• a.gtld-servers.net / nnn1-par6		•
	• b.gtld-servers.net / nnn1-elpar7		•
	• 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-nlams-1b		•
	• k.gtld-servers.net / nnn1-nlams-1b		•
	• l.gtld-servers.net / nnn1-nlams-1b		•
	• m.gtld-servers.net / nnn1-nlams-1c		•

4. SOA-Entries

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

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

Domain:	chatremix.com
Zone-Name:	chatremix.com
Primary:	ns2.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2021110968
Refresh:	10800
Retry:	1800
Expire:	604800
TTL:	1800
num Entries:	12

Domain:	www.chatremix.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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://chatremix.com/ 82.28.202.151	-14	10.097	T
Timeout - The operation has timed out

• http://www.chatremix.com/ 82.28.202.151	-14	10.030	T
Timeout - The operation has timed out

• https://chatremix.com/ 82.28.202.151	-14	10.037	T
Timeout - The operation has timed out

• https://www.chatremix.com/ 82.28.202.151	-14	10.023	T
Timeout - The operation has timed out

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

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

• https://82.28.202.151/ 82.28.202.151	-14	10.150	T
Timeout - The operation has timed out

7. Comments

	1. General Results, most used to calculate the result
A	name "chatremix.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: 88398 (complete: 228216)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: chatremix.com has only one ip address.
	Warning: Only one ip address found: www.chatremix.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: chatremix.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.chatremix.com has no ipv6 address.
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.
	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 chatremix.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.chatremix.com, 1 ip addresses.
A	Good: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.chatremix.com
B	Bad: _mta-sts TXT found, but invalid
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 14 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 8 Name Servers.
A	Info:: 14 Queries complete, 14 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.no-ip.com (194.62.181.53, 2a07:dc00:1810::53), ns1.no-ip.com (194.62.181.53, 2a07:dc00:1810::53), ns2.no-ip.com (194.62.180.53, 2a07:dc00:180::53), ns3.no-ip.com (204.16.255.53, 2a07:dc00:2550::53), ns4.no-ip.com (204.16.254.53, 2620:0:2e64::53)
A	Good (1 - 3.0):: An average of 1.8 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 8 different Name Servers found: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com, static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, 3 Name Servers included in Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, 5 Name Servers included in 1 Zone definitions: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com, 1 Name Servers listed in SOA.Primary: ns2.no-ip.com.
A	Good: Only one SOA.Primary Name Server found.: ns2.no-ip.com.
	Error: SOA.Primary Name Server not included in the delegation set.: ns2.no-ip.com.
X	Fatal: 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.: ns1.no-ip.com (194.62.181.53): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com.
X	Fatal: 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.: ns1.no-ip.com (2a07:dc00:1810::53): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com.
X	Fatal: 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.: ns2.no-ip.com (194.62.180.53): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com.
X	Fatal: 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.: ns2.no-ip.com (2a07:dc00:180::53): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com.
X	Fatal: 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.: ns3.no-ip.com (204.16.255.53): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com.
X	Fatal: 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.: ns3.no-ip.com (2a07:dc00:2550::53): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com.
X	Fatal: 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.: ns4.no-ip.com (204.16.254.53): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com.
X	Fatal: 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.: ns4.no-ip.com (2620:0:2e64::53): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com.
X	Fatal: 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.no-ip.com (194.62.181.53): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com.
X	Fatal: 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.: static-1.no-ip.com (194.62.181.53): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com.
X	Fatal: 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.: static-2.no-ip.com (45.77.3.172): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com.
X	Fatal: 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.: static-3.no-ip.com (104.207.132.142): Delegation: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com, Zone: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com. Name Servers defined in Delegation, missing in Zone: static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com.Name Servers defined in Zone, missing in Delegation: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.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: 8 different Name Servers found
A	Good: Some Name Servers have IPv6 addresses: 4 Name Servers with IPv6 found (4 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.: 8 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: no-ip.com
A	Good: Name servers with different Country locations found: 8 Name Servers, 3 Countries: GB, NL, US
A	Info: Ipv4-Subnet-list: 8 Name Servers, 4 different subnets (first Byte): 104., 194., 204., 45., 4 different subnets (first two Bytes): 104.207., 194.62., 204.16., 45.77., 6 different subnets (first three Bytes): 104.207.132., 194.62.180., 194.62.181., 204.16.254., 204.16.255., 45.77.3.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 2 different subnets (first block): 2620:, 2a07:, 2 different subnets (first two blocks): 2620:0000:, 2a07:dc00:, 4 different subnets (first three blocks): 2620:0000:2e64:, 2a07:dc00:0180:, 2a07:dc00:1810:, 2a07:dc00:2550:, 4 different subnets (first four blocks): 2620:0000:2e64:0000:, 2a07:dc00:0180:0000:, 2a07:dc00:1810:0000:, 2a07:dc00:2550: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
	Nameserver doesn't pass all EDNS-Checks: ns2.no-ip.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
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://chatremix.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.28.202.151	-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.chatremix.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.28.202.151	-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: 160460 milliseconds, 160.460 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=TrustCor DV SSL CA - G2 - RSA, O=TrustCor Systems S. de R.L., C=PA				0	0	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
3839978853 leaf cert	CN=TrustCor DV SSL CA - G2 - RSA, O=TrustCor Systems S. de R.L., C=PA	2022-06-13 19:42:17	2023-06-13 19:42:16	chatremix.com - 1 entries

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

Small Code Update - wait one minute

11. Html-Content - Entries

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

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com, ns5.no-ip.com, static-1.no-ip.com, static-2.no-ip.com, static-3.no-ip.com

QNr.	Domain	Type	NS used
1	com	NS	d.root-servers.net (2001:500:2d::d)
	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	ns1.no-ip.com: 194.62.181.53, 2a07:dc00:1810::53	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
3	ns5.no-ip.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com
	Answer: ns1.no-ip.com 194.62.181.53, 2a07:dc00:1810::53
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
4	static-1.no-ip.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com
	Answer: ns1.no-ip.com 194.62.181.53, 2a07:dc00:1810::53
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
5	static-2.no-ip.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com
	Answer: ns1.no-ip.com 194.62.181.53, 2a07:dc00:1810::53
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
6	static-3.no-ip.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com
	Answer: ns1.no-ip.com 194.62.181.53, 2a07:dc00:1810::53
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
7	ns5.no-ip.com: 194.62.181.53	A	ns1.no-ip.com (2a07:dc00:1810::53)
8	ns5.no-ip.com: No AAAA record found	AAAA	ns1.no-ip.com (2a07:dc00:1810::53)
9	static-1.no-ip.com: 194.62.181.53	A	ns1.no-ip.com (2a07:dc00:1810::53)
10	static-1.no-ip.com: No AAAA record found	AAAA	ns1.no-ip.com (2a07:dc00:1810::53)
11	static-2.no-ip.com: 45.77.3.172	A	ns1.no-ip.com (2a07:dc00:1810::53)
12	static-2.no-ip.com: No AAAA record found	AAAA	ns1.no-ip.com (2a07:dc00:1810::53)
13	static-3.no-ip.com: 104.207.132.142	A	ns1.no-ip.com (2a07:dc00:1810::53)
14	static-3.no-ip.com: No AAAA record found	AAAA	ns1.no-ip.com (2a07:dc00:1810::53)

14. CAA - Entries

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

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
chatremix.com	firebase=chatremixback	ok	1
chatremix.com	v=spf1 include:_spf.firebasemail.com ~all	ok	1
www.chatremix.com	firebase=chatremixback	ok	1
www.chatremix.com	v=spf1 include:_spf.firebasemail.com ~all	ok	1
_acme-challenge.chatremix.com	firebase=chatremixback	missing entry or wrong length	1
_acme-challenge.chatremix.com	v=spf1 include:_spf.firebasemail.com ~all	missing entry or wrong length	1
_acme-challenge.www.chatremix.com	firebase=chatremixback	missing entry or wrong length	1
_acme-challenge.www.chatremix.com	v=spf1 include:_spf.firebasemail.com ~all	missing entry or wrong length	1
_acme-challenge.chatremix.com.chatremix.com	firebase=chatremixback	perhaps wrong	1
_acme-challenge.chatremix.com.chatremix.com	v=spf1 include:_spf.firebasemail.com ~all	perhaps wrong	1
_acme-challenge.www.chatremix.com.chatremix.com	firebase=chatremixback	perhaps wrong	1
_acme-challenge.www.chatremix.com.chatremix.com	v=spf1 include:_spf.firebasemail.com ~all	perhaps wrong	1
_acme-challenge.www.chatremix.com.www.chatremix.com	firebase=chatremixback	perhaps wrong	1
_acme-challenge.www.chatremix.com.www.chatremix.com	v=spf1 include:_spf.firebasemail.com ~all	perhaps wrong	1

16. DomainService - Entries

Type		Domain	Pref	Value	DNS-error	num Answers	Status	Description
MX		chatremix.com	5	aspmx.l.google.com	0	5	ok
	A			74.125.133.26	0	1	ok
	AAAA			2a00:1450:400c:c0c::1b	0	1	ok
	CNAME				0	0	ok
MX		chatremix.com	10	alt2.aspmx.l.google.com	0	5	ok
	A			142.251.9.26	0	1	ok
	AAAA			2a00:1450:4025:c03::1b	0	1	ok
	CNAME				0	0	ok
MX		chatremix.com	10	alt1.aspmx.l.google.com	0	5	ok
	A			142.250.153.26	0	1	ok
	AAAA			2a00:1450:4013:c16::1a	0	1	ok
	CNAME				0	0	ok
MX		chatremix.com	15	alt3.aspmx.l.google.com	0	5	ok
	A			142.250.150.27	0	1	ok
	AAAA			2a00:1450:4010:c1c::1b	0	1	ok
	CNAME				0	0	ok
MX		chatremix.com	15	alt4.aspmx.l.google.com	0	5	ok
	A			74.125.200.27	0	1	ok
	AAAA			2404:6800:4003:c00::1b	0	1	ok
	CNAME				0	0	ok
MX		www.chatremix.com	5	aspmx.l.google.com	0	5	ok
	A			66.102.1.26	0	1	ok
	AAAA			2a00:1450:400c:c03::1b	0	1	ok
	CNAME				0	0	ok
MX		www.chatremix.com	10	alt1.aspmx.l.google.com	0	5	ok
	A			142.250.153.26	0	1	ok
	AAAA			2a00:1450:4013:c16::1a	0	1	ok
	CNAME				0	0	ok
MX		www.chatremix.com	10	alt2.aspmx.l.google.com	0	5	ok
	A			142.251.9.26	0	1	ok
	AAAA			2a00:1450:4025:c03::1b	0	1	ok
	CNAME				0	0	ok
MX		www.chatremix.com	15	alt3.aspmx.l.google.com	0	5	ok
	A			142.250.150.26	0	1	ok
	AAAA			2a00:1450:4010:c1c::1b	0	1	ok
	CNAME				0	0	ok
MX		www.chatremix.com	15	alt4.aspmx.l.google.com	0	5	ok
	A			74.125.200.27	0	1	ok
	AAAA			2404:6800:4003:c00::1b	0	1	ok
	CNAME				0	0	ok
_mta-sts	TXT	_mta-sts.chatremix.com		v=spf1 include:_spf.firebasemail.com ~all			2	A MTA-STS TXT Entry (Mail Transfer Agent Strict Transport Security) must start with "'v=STSv1". Do you really want to create a MTA-STS? Or is it the effect of a wildcard * DNS?

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=e9ff250f-73ed-4009-9271-78137e5eeff7

Last Result: https://check-your-website.server-daten.de/?q=chatremix.com - 2023-08-02 00:00:09

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

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