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


Update: 2020-03-04 - now 90 days later. All affected Letsencrypt certificates should be renewed. Time to remove that Info.




X

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

Checked:
06.04.2020 20:57:08


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
itlife.pro
A

yes
1
0

AAAA

yes


www.itlife.pro

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations

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



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 33853, Flags 256



Public Key with Algorithm 8, KeyTag 48903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.04.2020, 00:00:00 +, Signature-Inception: 01.04.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: pro
pro
2 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.04.2020, 17:00:00 +, Signature-Inception: 06.04.2020, 16:00:00 +, KeyTag 48903, Signer-Name: (root)



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



4 DNSKEY RR found



Public Key with Algorithm 7, KeyTag 18893, Flags 256



Public Key with Algorithm 7, KeyTag 34262, Flags 256



Public Key with Algorithm 7, KeyTag 44605, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 7, KeyTag 47221, Flags 257 (SEP = Secure Entry Point)



2 RRSIG RR to validate DNSKEY RR found



Algorithm: 7, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.04.2020, 15:17:58 +, Signature-Inception: 01.04.2020, 14:17:58 +, KeyTag 34262, Signer-Name: pro



Algorithm: 7, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.04.2020, 15:17:58 +, Signature-Inception: 01.04.2020, 14:17:58 +, KeyTag 47221, Signer-Name: pro



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 34262 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 47221 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 47221, DigestType 1 and Digest "AMv8vcnG5ln7I4WzmC6T6Y1xBS0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 47221, DigestType 2 and Digest "WhA4nigssD8Qg8FmKyGLl8/mECS5kcfF2LtWha1kh8o=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: itlife.pro
itlife.pro
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.Bitmap: A, RRSIG



0 DNSKEY RR found





Zone: www.itlife.pro
www.itlife.pro
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.itlife.pro
  ns1.reg.ru

itlife.pro
  ns1.reg.ru / ns6.reg.ru
176.99.13.11
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.13
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.15
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.17
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
194.58.117.11
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.13
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.15
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.17
Moscow/Russia (RU) - Domain names registrar REG.RU


 
2a00:f940:4::47
Cheryomushki District/Moscow/Russia (RU) - Reg.Ru SRS Infrastructure


  ns2.reg.ru / ns6.reg.ru
176.99.13.12
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.14
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.16
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.18
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
194.58.117.12
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.14
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.16
Moscow/Russia (RU) - Domain names registrar REG.RU


 
194.58.117.18
Moscow/Russia (RU) - Domain names registrar REG.RU


 
2a00:f940:5::190
Cheryomushki District/Moscow/Russia (RU) - Reg.Ru SRS Infrastructure

pro
  a0.pro.afilias-nst.info / ns014b.app4.nrt1.afilias-nst.info


  a2.pro.afilias-nst.info / 1.fra.pch


  b0.pro.afilias-nst.org / ns014b.app25.ams2.afilias-nst.info


  b2.pro.afilias-nst.org / 4.fra.pch


  c0.pro.afilias-nst.info / ns014b.app6.ams2.afilias-nst.info


  d0.pro.afilias-nst.org / app21.iad1.hosts.meta.redstone.afilias-nst.info-2


4. SOA-Entries


Domain:pro
Zone-Name:
Primary:a0.pro.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013105210
Refresh:10800
Retry:3600
Expire:2764800
TTL:900
num Entries:6


Domain:itlife.pro
Zone-Name:
Primary:ns1.reg.ru
Mail:hostmaster.ns1.reg.ru
Serial:1586197962
Refresh:14400
Retry:3600
Expire:604800
TTL:10800
num Entries:18


Domain:www.itlife.pro
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







7. Comments


1. General Results, most used to calculate the result

Aname "itlife.pro" is domain, public suffix is "pro", top-level-domain-type is "generic-restricted", tld-manager is "Registry Services Corporation dba RegistryPro"
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

2. DNS- and NameServer - Checks

AGood: 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: ns1.reg.ru,ns2.reg.ru
AGood: Nameserver supports TCP connections: 18 good Nameserver
AGood: Nameserver supports Echo Capitalization: 18 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 18 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 18 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.reg.ru: 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

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: 69790 milliseconds, 69.790 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 (alpha)

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
itlife.pro
0

no CAA entry found
1
0
pro
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
itlife.pro

ok
1
0
_acme-challenge.itlife.pro

Name Error - The domain name does not exist
1
0
_acme-challenge.itlife.pro.itlife.pro

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=6290566c-3202-4ea3-959a-a2bb35c60321


Last Result: https://check-your-website.server-daten.de/?q=itlife.pro - 2020-04-06 20:57:08


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

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