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



X

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

Checked:
21.11.2020 14:57:32


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
pcdytk7afignxazh.myfritz.net
A
85.197.48.100
Cologne/North Rhine-Westphalia/Germany (DE) - NetCologne Gesellschaft fur Telekommunikation mbH
Hostname: xdsl-85-197-48-100.nc.de
yes
1
0

AAAA
2001:4dd0:af0a:d40b:3a10:d5ff:fe0b:df12
Cologne/North Rhine-Westphalia/Germany (DE) - NetCologne GmbH

yes


www.pcdytk7afignxazh.myfritz.net

Name Error
yes
1
0
*.pcdytk7afignxazh.myfritz.net
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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 26116, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.12.2020, 00:00:00 +, Signature-Inception: 20.11.2020, 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 8, KeyTag 35886, DigestType 2 and Digest eGKyf19Rbr4ZaARE1M5edimBkxhCxGXwAjZAHYvZc+4=



1 RRSIG RR to validate DS RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.12.2020, 05:00:00 +, Signature-Inception: 21.11.2020, 04:00:00 +, KeyTag 26116, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 15314, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.12.2020, 17:28:30 +, Signature-Inception: 20.11.2020, 17:23:30 +, KeyTag 35886, Signer-Name: net



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



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

Zone: myfritz.net
myfritz.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 "e3bp8sarahcdm1q5qg86ual91n828ae4" between the hashed NSEC3-owner "e3bismm17ii88a33eud8h49143nb4nhr" and the hashed NextOwner "e3brrrcnhba8kjdmo4tsoq9f6vih09ac". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner e3bismm17ii88a33eud8h49143nb4nhr.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 27.11.2020, 08:06:37 +, Signature-Inception: 20.11.2020, 06:56:37 +, KeyTag 15314, 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 "a1ruuffjkct2q54p78f8ejgj8jbk7i8b". So that domain name is the Closest Encloser of "myfritz.net". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 25.11.2020, 08:13:20 +, Signature-Inception: 18.11.2020, 07:03:20 +, KeyTag 15314, Signer-Name: net



0 DNSKEY RR found




Zone: pcdytk7afignxazh.myfritz.net
pcdytk7afignxazh.myfritz.net
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.pcdytk7afignxazh.myfritz.net
www.pcdytk7afignxazh.myfritz.net
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.pcdytk7afignxazh.myfritz.net
  ns2.myfritz.net

pcdytk7afignxazh.myfritz.net
  ns2.myfritz.net
212.42.244.13
Berlin/Land Berlin/Germany (DE) - D-hosting die Rackspace & Connectivity GmbH


 
2001:bf0:244::13
Berlin/Land Berlin/Germany (DE) - Advanced Leased Lines

myfritz.net
  ns1.myfritz.net
217.110.95.230
Berlin/Land Berlin/Germany (DE) - Colt Technology Services


 
2001:920:197e:400::4
Frankfurt am Main/Hesse/Germany (DE) - Colt Technology Services GmbH


  ns2.myfritz.net
212.42.244.13
Berlin/Land Berlin/Germany (DE) - D-hosting die Rackspace & Connectivity GmbH


 
2001:bf0:244::13
Berlin/Land Berlin/Germany (DE) - Advanced Leased Lines


  ns3.myfritz.net
212.42.224.76
Berlin/Land Berlin/Germany (DE) - D-Hosting GmbH


 
2001:bf0:212::76
Berlin/Land Berlin/Germany (DE) - Advanced Leased Lines

net
  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


4. SOA-Entries


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


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


Domain:myfritz.net
Zone-Name:myfritz.net
Primary:ns2.myfritz.net
Mail:admin.avm.de
Serial:3022449116
Refresh:20
Retry:20
Expire:86400
TTL:1
num Entries:4


Domain:myfritz.net
Zone-Name:myfritz.net
Primary:ns2.myfritz.net
Mail:admin.avm.de
Serial:3022449146
Refresh:20
Retry:20
Expire:86400
TTL:1
num Entries:2


Domain:pcdytk7afignxazh.myfritz.net
Zone-Name:myfritz.net
Primary:ns2.myfritz.net
Mail:admin.avm.de
Serial:3022449149
Refresh:20
Retry:20
Expire:86400
TTL:1
num Entries:2


Domain:www.pcdytk7afignxazh.myfritz.net
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


:

:
DomainnameHttp-StatusredirectSec.G
• http://pcdytk7afignxazh.myfritz.net/
85.197.48.100 No GZip used - 184 / 193 - 95.34 % possible
200

Html is minified: 142.96 %
0.060
H
small visible content (num chars: 48)
Yes Congratulations! The HTTP Server is working!
Server: SimpleHTTP/0.6 Python/3.8.3
Date: Sat, 21 Nov 2020 13:58:06 GMT
Content-type: text/html
Content-Length: 193
Last-Modified: Sat, 21 Nov 2020 11:48:37 GMT

• http://pcdytk7afignxazh.myfritz.net/
2001:4dd0:af0a:d40b:3a10:d5ff:fe0b:df12
-14

10.013
T
Timeout - The operation has timed out

• https://pcdytk7afignxazh.myfritz.net/
85.197.48.100
-14

10.030
T
Timeout - The operation has timed out

• https://pcdytk7afignxazh.myfritz.net/
2001:4dd0:af0a:d40b:3a10:d5ff:fe0b:df12
-14

10.013
T
Timeout - The operation has timed out

• http://pcdytk7afignxazh.myfritz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
85.197.48.100
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 121.19 %
0.063
A
File not found
Visible Content: Error response Error code: 404 Message: File not found. Error code explanation: HTTPStatus.NOT_FOUND - Nothing matches the given URI.
Server: SimpleHTTP/0.6 Python/3.8.3
Date: Sat, 21 Nov 2020 13:58:37 GMT
Connection: close
Content-Type: text/html;charset=utf-8
Content-Length: 469

• http://pcdytk7afignxazh.myfritz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2001:4dd0:af0a:d40b:3a10:d5ff:fe0b:df12
-14

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

• https://85.197.48.100/
85.197.48.100
-14

10.014
T
Timeout - The operation has timed out

• https://[2001:4dd0:af0a:d40b:3a10:d5ff:fe0b:df12]/
2001:4dd0:af0a:d40b:3a10:d5ff:fe0b:df12
-14

10.030
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "pcdytk7afignxazh.myfritz.net" is domain, public suffix is ".myfritz.net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 5892 (complete: 131120)
Agood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: pcdytk7afignxazh.myfritz.net has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: pcdytk7afignxazh.myfritz.net has 1 ipv4, 1 ipv6 addresses
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
Agood - only one version with Http-Status 200
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (2 urls)
http://pcdytk7afignxazh.myfritz.net/ 85.197.48.100


Url with incomplete Content-Type - header - missing charset
Hfatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Khttp://pcdytk7afignxazh.myfritz.net/ 85.197.48.100, Status 200

http://pcdytk7afignxazh.myfritz.net/ 2001:4dd0:af0a:d40b:3a10:d5ff:fe0b:df12, Status -14
configuration problem - different ip addresses with different status
Khttp://pcdytk7afignxazh.myfritz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.197.48.100, Status 404

http://pcdytk7afignxazh.myfritz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:4dd0:af0a:d40b:3a10:d5ff:fe0b:df12, Status -14
configuration problem - different ip addresses with different status
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain pcdytk7afignxazh.myfritz.net, 2 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 pcdytk7afignxazh.myfritz.net, 2 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 4 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 4 Queries complete, 4 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: 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.ns2.myfritz.net (2001:bf0:244::13, 212.42.244.13), ns3.myfritz.net (2001:bf0:212::76, 212.42.224.76)
AGood (1 - 3.0):: An average of 1.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns1.myfritz.net, ns2.myfritz.net, ns3.myfritz.net, 2 Name Servers included in Delegation: ns2.myfritz.net, ns3.myfritz.net, 3 Name Servers included in 1 Zone definitions: ns1.myfritz.net, ns2.myfritz.net, ns3.myfritz.net, 1 Name Servers listed in SOA.Primary: ns2.myfritz.net.
AGood: Only one SOA.Primary Name Server found.: ns2.myfritz.net.
AGood: SOA.Primary Name Server included in the delegation set.: ns2.myfritz.net.
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.: ns1.myfritz.net (217.110.95.230): Delegation: ns2.myfritz.net, ns3.myfritz.net, Zone: ns1.myfritz.net, ns2.myfritz.net, ns3.myfritz.net. Name Servers defined in Zone, missing in Delegation: ns1.myfritz.net.
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.: ns1.myfritz.net (2001:920:197e:400::4): Delegation: ns2.myfritz.net, ns3.myfritz.net, Zone: ns1.myfritz.net, ns2.myfritz.net, ns3.myfritz.net. Name Servers defined in Zone, missing in Delegation: ns1.myfritz.net.
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.: ns2.myfritz.net (212.42.244.13): Delegation: ns2.myfritz.net, ns3.myfritz.net, Zone: ns1.myfritz.net, ns2.myfritz.net, ns3.myfritz.net. Name Servers defined in Zone, missing in Delegation: ns1.myfritz.net.
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.: ns2.myfritz.net (2001:bf0:244::13): Delegation: ns2.myfritz.net, ns3.myfritz.net, Zone: ns1.myfritz.net, ns2.myfritz.net, ns3.myfritz.net. Name Servers defined in Zone, missing in Delegation: ns1.myfritz.net.
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.: ns3.myfritz.net (212.42.224.76): Delegation: ns2.myfritz.net, ns3.myfritz.net, Zone: ns1.myfritz.net, ns2.myfritz.net, ns3.myfritz.net. Name Servers defined in Zone, missing in Delegation: ns1.myfritz.net.
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.: ns3.myfritz.net (2001:bf0:212::76): Delegation: ns2.myfritz.net, ns3.myfritz.net, Zone: ns1.myfritz.net, ns2.myfritz.net, ns3.myfritz.net. Name Servers defined in Zone, missing in Delegation: ns1.myfritz.net.
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: 3 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 3 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.: 3 Name Servers, 1 Top Level Domain: myfritz.net
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:
Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: DE
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 212., 217., 2 different subnets (first two Bytes): 212.42., 217.110., 3 different subnets (first three Bytes): 212.42.224., 212.42.244., 217.110.95.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2001:, 2 different subnets (first two blocks): 2001:0920:, 2001:0bf0:, 3 different subnets (first three blocks): 2001:0920:197e:, 2001:0bf0:0212:, 2001:0bf0:0244:, 3 different subnets (first four blocks): 2001:0920:197e:0400:, 2001:0bf0:0212:0000:, 2001:0bf0:0244:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns2.myfritz.net: 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.
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.

3. Content- and Performance-critical Checks

http://pcdytk7afignxazh.myfritz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:4dd0:af0a:d40b:3a10:d5ff:fe0b:df12
-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://pcdytk7afignxazh.myfritz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:4dd0:af0a:d40b:3a10:d5ff:fe0b:df12, Status -14

http://pcdytk7afignxazh.myfritz.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.197.48.100, Status 404
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
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: 110834 milliseconds, 110.834 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)

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 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. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.myfritz.net, ns2.myfritz.net, ns3.myfritz.net

QNr.DomainTypeNS used
1
net
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
ns1.myfritz.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns2.myfritz.net, ns3.myfritz.net

Answer: ns2.myfritz.net
2001:bf0:244::13, 212.42.244.13

Answer: ns3.myfritz.net
2001:bf0:212::76, 212.42.224.76
3
ns1.myfritz.net: 217.110.95.230
A
ns2.myfritz.net (2001:bf0:244::13)
4
ns1.myfritz.net: 2001:920:197e:400::4
AAAA
ns2.myfritz.net (2001:bf0:244::13)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
pcdytk7afignxazh.myfritz.net
0

no CAA entry found
1
0
myfritz.net
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
pcdytk7afignxazh.myfritz.net

ok
1
0
_acme-challenge.pcdytk7afignxazh.myfritz.net

Name Error - The domain name does not exist
1
0
_acme-challenge.pcdytk7afignxazh.myfritz.net.pcdytk7afignxazh.myfritz.net

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=b21933c1-1f6d-493f-89a8-c9447ad9285a


Last Result: https://check-your-website.server-daten.de/?q=pcdytk7afignxazh.myfritz.net - 2020-11-21 14:57:32


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

<a href="https://check-your-website.server-daten.de/?q=pcdytk7afignxazh.myfritz.net" target="_blank">Check this Site: pcdytk7afignxazh.myfritz.net</a>