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





1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mytel.com
A
69.172.201.153
Los Angeles/California/United States (US) - Cogeco Peer 1
No Hostname found
yes
1
0

AAAA

yes


www.mytel.com
A
69.172.201.153
Los Angeles/California/United States (US) - Cogeco Peer 1
No Hostname found
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (some minor bugs wildcard + nsec/nsec3)

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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.11.2019, 00:00:00 +, Signature-Inception: 31.10.2019, 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



1 RRSIG RR to validate DS RR found



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



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 12163, Flags 256



Public Key with Algorithm 8, KeyTag 17708, 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: 22.11.2019, 19:24:21 +, Signature-Inception: 07.11.2019, 19: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: mytel.com
mytel.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 "knaa9cm3pk2vos7msgs1ojho8jgdpetv" between the hashed NSEC3-owner "kna9irqi9ddimavonddtd7h21jko67pl" and the hashed NextOwner "knaaa2b1gc1u3e844dvqdsi0s4blh66v". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner kna9irqi9ddimavonddtd7h21jko67pl.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 14.11.2019, 06:21:23 +, Signature-Inception: 07.11.2019, 05:11:23 +, KeyTag 12163, Signer-Name: com



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
www.mytel.com
  ns1.uniregistrymarket.link


  ns2.uniregistrymarket.link

mytel.com
  buy.internettraffic.com
35.211.36.175
Ashburn/Virginia/United States (US) - Google LLC


 
52.89.18.51
Portland/Oregon/United States (US) - Amazon.com, Inc.


  ns1.uniregistrymarket.link
35.211.36.175
Ashburn/Virginia/United States (US) - Google LLC


 
52.89.18.51
Portland/Oregon/United States (US) - Amazon.com, Inc.


  ns2.uniregistrymarket.link
18.217.16.210
Dublin/Ohio/United States (US) - Amazon.com, Inc.


 
34.90.60.247
Ashburn/Virginia/United States (US) - Google LLC


  sell.internettraffic.com
18.217.16.210
Dublin/Ohio/United States (US) - Amazon.com, Inc.


 
34.90.60.247
Ashburn/Virginia/United States (US) - Google LLC

com
  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:com
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1573265947
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:11


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


Domain:mytel.com
Zone-Name:
Primary:ns1.uniregistrymarket.link
Mail:hostmaster.hostingnet.com
Serial:1571750222
Refresh:10800
Retry:3600
Expire:604800
TTL:86400
num Entries:8


Domain:www.mytel.com
Zone-Name:
Primary:ns1.uniregistrymarket.link
Mail:hostmaster.hostingnet.com
Serial:1571750222
Refresh:10800
Retry:3600
Expire:604800
TTL:86400
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://mytel.com/
69.172.201.153 GZip used - 773 / 1556 - 50.32 %
200

Html is minified: 376.76 %
0.344
H
Server: nginx
Date: Sat, 09 Nov 2019 02:20:15 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
X-DIS-Request-ID: 273e3ae477f07cf192904ebaba63e512
P3P: CP="NON DSP COR ADMa OUR IND UNI COM NAV INT"
Cache-Control: no-cache
Content-Encoding: gzip

• http://www.mytel.com/
69.172.201.153 GZip used - 773 / 1556 - 50.32 %
200

Html is minified: 376.76 %
0.347
H
Server: nginx
Date: Sat, 09 Nov 2019 02:20:15 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
X-DIS-Request-ID: e26a6bba2e006426fff3173f1700b859
P3P: CP="NON DSP COR ADMa OUR IND UNI COM NAV INT"
Cache-Control: no-cache
Content-Encoding: gzip

• https://mytel.com/
69.172.201.153
-2

1.530
V
ConnectFailure - Unable to connect to the remote server

• https://www.mytel.com/
69.172.201.153
-2

1.516
V
ConnectFailure - Unable to connect to the remote server

• http://mytel.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
69.172.201.153 GZip used - 773 / 1556 - 50.32 %
Inline-JavaScript (∑/total): 1/1099 Inline-CSS (∑/total): 0/0
200

Html is minified: 376.76 %
0.346

Visible Content:
Server: nginx
Date: Sat, 09 Nov 2019 02:20:18 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
X-DIS-Request-ID: 54d4b8b5ce87e6f165296c88ebd57246
P3P: CP="NON DSP COR ADMa OUR IND UNI COM NAV INT"
Cache-Control: no-cache
Content-Encoding: gzip

• http://www.mytel.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
69.172.201.153 GZip used - 773 / 1556 - 50.32 %
Inline-JavaScript (∑/total): 1/1099 Inline-CSS (∑/total): 0/0
200

Html is minified: 376.76 %
0.343

Visible Content:
Server: nginx
Date: Sat, 09 Nov 2019 02:20:19 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
X-DIS-Request-ID: 0713378d76847c5d55ce31514ef058f7
P3P: CP="NON DSP COR ADMa OUR IND UNI COM NAV INT"
Cache-Control: no-cache
Content-Encoding: gzip

7. Comments


1. General Results, most used to calculate the result

Aname "mytel.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
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.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (4 urls)
http://mytel.com/ 69.172.201.153


Url with incomplete Content-Type - header - missing charset
http://www.mytel.com/ 69.172.201.153


Url with incomplete Content-Type - header - missing charset
http://mytel.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.172.201.153


Url with incomplete Content-Type - header - missing charset
http://www.mytel.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.172.201.153


Url with incomplete Content-Type - header - missing charset
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
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.
Vhttps://mytel.com/ 69.172.201.153
-2

connect failure - perhaps firewall
Vhttps://www.mytel.com/ 69.172.201.153
-2

connect failure - perhaps firewall

2. DNS- and NameServer - Checks

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.: sell.internettraffic.com (18.217.16.210): Delegation: buy.internettraffic.com,sell.internettraffic.com, Zone: ns1.uniregistrymarket.link,ns2.uniregistrymarket.link
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.: sell.internettraffic.com (34.90.60.247): Delegation: buy.internettraffic.com,sell.internettraffic.com, Zone: ns1.uniregistrymarket.link,ns2.uniregistrymarket.link
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.uniregistrymarket.link (18.217.16.210): Delegation: buy.internettraffic.com,sell.internettraffic.com, Zone: ns1.uniregistrymarket.link,ns2.uniregistrymarket.link
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.uniregistrymarket.link (34.90.60.247): Delegation: buy.internettraffic.com,sell.internettraffic.com, Zone: ns1.uniregistrymarket.link,ns2.uniregistrymarket.link
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.uniregistrymarket.link (35.211.36.175): Delegation: buy.internettraffic.com,sell.internettraffic.com, Zone: ns1.uniregistrymarket.link,ns2.uniregistrymarket.link
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.uniregistrymarket.link (52.89.18.51): Delegation: buy.internettraffic.com,sell.internettraffic.com, Zone: ns1.uniregistrymarket.link,ns2.uniregistrymarket.link
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.: buy.internettraffic.com (35.211.36.175): Delegation: buy.internettraffic.com,sell.internettraffic.com, Zone: ns1.uniregistrymarket.link,ns2.uniregistrymarket.link
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.: buy.internettraffic.com (52.89.18.51): Delegation: buy.internettraffic.com,sell.internettraffic.com, Zone: ns1.uniregistrymarket.link,ns2.uniregistrymarket.link
AInfo: Nameserver mit different domain names found. May be a problem with DNS-Updates
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 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.

3. Content- and Performance-critical Checks

http://mytel.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.172.201.153
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.mytel.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 69.172.201.153
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 61723 milliseconds, 61.723 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:

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


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.mytel.com
0

no CAA entry found
1
0
mytel.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
mytel.com

ok
1
0
www.mytel.com

ok
1
0
_acme-challenge.mytel.com

missing entry or wrong length
1
0
_acme-challenge.www.mytel.com

missing entry or wrong length
1
0
_acme-challenge.mytel.com.mytel.com

perhaps wrong
1
0
_acme-challenge.www.mytel.com.mytel.com

perhaps wrong
1
0
_acme-challenge.www.mytel.com.www.mytel.com

perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=86ca10ac-be4f-469f-98ca-4b363cc2c591


Last Result: https://check-your-website.server-daten.de/?q=mytel.com - 2020-04-27 00:39:48


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

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