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


Info: Problems with 3.048.289 Letsencrypt certificates (378.325 accounts). They must be revoked (revocation starts 2020-03-04 20:00 UTC) - see Revoking certain certificates on March 4. Update 2020-03-07: Good news: Mass-revocation is canceled.

This tool: A check (SerialNumber) is added. Letsencrypt has published a list of critical SerialNumbers, this list is checked. See the part "9. Certificates". If there is a warning, renew that certificate and replace the current certificate.




U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
28.04.2020 17:48:41


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mailman.asia

Name Error
yes
1
0
www.mailman.asia

Name Error
yes
1
0


2. DNSSEC

Info: The Xml-split has triggered some hidden bugs. Now it looks ok.
If root or the top level zone isn't validated, it's buggy.
Both green and your domain is red -> it's your domain.

Zone (*)DNSSEC - Informations

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



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 12.05.2020, 00:00:00 +, Signature-Inception: 21.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: asia
asia
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: 11.05.2020, 05:00:00 +, Signature-Inception: 28.04.2020, 04: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 4799, Flags 256



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



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



Public Key with Algorithm 7, KeyTag 61067, Flags 256



3 RRSIG RR to validate DNSKEY RR found



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 16.05.2020, 15:33:21 +, Signature-Inception: 25.04.2020, 14:33:21 +, KeyTag 11136, Signer-Name: asia



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 16.05.2020, 15:33:21 +, Signature-Inception: 25.04.2020, 14:33:21 +, KeyTag 13890, Signer-Name: asia



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 16.05.2020, 15:33:21 +, Signature-Inception: 25.04.2020, 14:33:21 +, KeyTag 61067, Signer-Name: asia



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



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 13890, DigestType 1 and Digest "ozpB+bMelFyzN5/DZmOIcDiSdXc=" 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 13890, DigestType 2 and Digest "9/GwNHnOIAoGgBWCWNG3klsKXyc+VOa950LRMhTdmcs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: mailman.asia
mailman.asia
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: NS, DS, RRSIG

Zone: www.mailman.asia
www.mailman.asia
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.mailman.asia
  a0.asia.afilias-nst.info

mailman.asia
  a0.asia.afilias-nst.info

asia
  a0.asia.afilias-nst.info / ns004a.app32.nrt1.afilias-nst.info


  a2.asia.afilias-nst.info / 2.ber.pch


  b0.asia.afilias-nst.asia / ns004b.app27.ams2.afilias-nst.info


  b2.asia.afilias-nst.org / 5.fra.pch


  c0.asia.afilias-nst.info / ns004a.app2.ams2.afilias-nst.info


  d0.asia.afilias-nst.asia / ns004b.app3.ams2.afilias-nst.info


4. SOA-Entries


Domain:asia
Zone-Name:
Primary:a0.asia.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2008397292
Refresh:3600
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:mailman.asia
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.mailman.asia
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 "mailman.asia" is domain, public suffix is "asia", top-level-domain-type is "sponsored", tld-manager is "DotAsia Organisation Ltd."
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

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: afilias-nst.info
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
Nameserver doesn't pass all EDNS-Checks: a0.asia.afilias-nst.info: 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.
Nameserver doesn't pass all EDNS-Checks: a0.asia.afilias-nst.info: 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

Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. 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: 17787 milliseconds, 17.787 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
asia
0

no CAA entry found
1
0


14. TXT - Entries

No TXT entries found


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=c79bdcd3-513c-407c-a5df-45cb5c3ee050


Last Result: https://check-your-website.server-daten.de/?q=mailman.asia - 2020-04-28 17:48:41


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

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