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




R

Redirect to non existing domain

Checked:
02.07.2019 16:00:44


Older results


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
fmradiords.com
A
31.220.20.22
London/England/United Kingdom (GB) - HOSTINGER GB
No Hostname found
yes
2
0

AAAA

yes


www.fmradiords.com
C
fmradiords.com
yes
1
0

A
31.220.20.22
London/England/United Kingdom (GB) - HOSTINGER GB
No Hostname found
yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)

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



Public Key with Algorithm 8, KeyTag 59944, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.07.2019, 00:00:00, Signature-Inception: 01.07.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



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.07.2019, 05:00:00, Signature-Inception: 02.07.2019, 04:00:00, KeyTag 59944, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 3800, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.07.2019, 18:25:33, Signature-Inception: 01.07.2019, 18:20:33, 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: fmradiords.com
fmradiords.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 domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.



0 DNSKEY RR found





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


3. Name Servers

DomainNameserverNS-IP
fmradiords.com
  ns1.hostinger.es / ns1.hostinger.com
31.170.163.241
Greenville/South Carolina/United States (US) - HOSTINGER US


  ns2.hostinger.es / ns2.hostinger.com
31.220.23.1
Manchester/England/United Kingdom (GB) - HOSTINGER GB


  ns3.hostinger.es / ns3.hostinger.com
173.192.183.247
Seattle/Washington/United States (US) - SoftLayer


  ns4.hostinger.es / ns4.hostinger.com
31.170.164.249
London/England/United Kingdom (GB) - HOSTINGER GB

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


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


Domain:fmradiords.com
Primary:ns1.hostinger.es
Mail:hostmaster.fmradiords.com
Serial:2019070100
Refresh:28800
Retry:7200
Expire:604800
TTL:86400
num Entries:4


5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://fmradiords.com/
31.220.20.22
301
https://web.fmradiords.com
0.074
E
Connection: close
Content-Type: text/html
Content-Length: 617
Date: Tue, 02 Jul 2019 14:01:24 GMT
Location: https://web.fmradiords.com

• http://www.fmradiords.com/
31.220.20.22
301
https://web.fmradiords.com
0.067
E
Connection: close
Content-Type: text/html
Content-Length: 617
Date: Tue, 02 Jul 2019 14:01:24 GMT
Location: https://web.fmradiords.com

• https://fmradiords.com/
31.220.20.22
200

0.450
B
Connection: close
Content-Type: text/html
Last-Modified: Mon, 01 Jul 2019 19:40:52 GMT
Etag: "7e-5d1a61c4-db75107e161961a4;;;"
Accept-Ranges: bytes
Content-Length: 126
Date: Tue, 02 Jul 2019 14:01:25 GMT
Alt-Svc: quic=":443"; ma=2592000; v="35,39,43,44,46", h3-20=":443"; ma=2592000

• https://www.fmradiords.com/
31.220.20.22
200

0.403
B
Connection: close
Content-Type: text/html
Last-Modified: Mon, 01 Jul 2019 19:40:52 GMT
Etag: "7e-5d1a61c4-db75107e161961a4;;;"
Accept-Ranges: bytes
Content-Length: 126
Date: Tue, 02 Jul 2019 14:01:25 GMT
Alt-Svc: quic=":443"; ma=2592000; v="35,39,43,44,46", h3-20=":443"; ma=2592000

• https://web.fmradiords.com

-1

0.167
R
NameResolutionFailure - The remote name could not be resolved: 'web.fmradiords.com'

• http://fmradiords.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
31.220.20.22
404

0.073
A
Not Found
Visible Content:
Connection: close
Content-Type: text/html
Content-Length: 166
Date: Tue, 02 Jul 2019 14:01:26 GMT

• http://www.fmradiords.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
31.220.20.22
404

0.077
A
Not Found
Visible Content:
Connection: close
Content-Type: text/html
Content-Length: 166
Date: Tue, 02 Jul 2019 14:01:26 GMT

6. Comments (GZip / Html minfied / Cache-Control is beta)

Aname "fmradiords.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
Agood: destination is https
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)
https://fmradiords.com/ 31.220.20.22


Url with incomplete Content-Type - header - missing charset
https://www.fmradiords.com/ 31.220.20.22


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


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


Url with incomplete Content-Type - header - missing charset
Bhttps://fmradiords.com/ 31.220.20.22
200

Missing HSTS-Header
Bhttps://www.fmradiords.com/ 31.220.20.22
200

Missing HSTS-Header
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.
CError - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
Ehttp://fmradiords.com/ 31.220.20.22
301
https://web.fmradiords.com
Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Ehttp://www.fmradiords.com/ 31.220.20.22
301
https://web.fmradiords.com
Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
OOld connection: SHA1 as Hash Algorithm is deprecated. Switch to SHA256 or SHA384. If your certificate has SHA256, first check your domain via ssllabs.com and update weak Cipher Suites. Forward Secrecy support is required. The part "Cipher Suites" should have a preference. First Cipher Suite with SHA instead of SHA256 or higher - that's the problem, change that. If that doesn't help, check if there is an old Firewall / router or something else, that supports only SHA1. Update that component.
Rhttp://fmradiords.com/ 31.220.20.22
301
https://web.fmradiords.com
redirect to non existing domain
Rhttp://www.fmradiords.com/ 31.220.20.22
301
https://web.fmradiords.com
redirect to non existing domain
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 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.
AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. 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: 41377 milliseconds, 41.377 seconds


7. Connections (http/2 - check is BETA)

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
fmradiords.com
31.220.20.22
443
ok
Tls12
ECDH Ephermal
256
Aes128
128
Sha1
error checking OCSP stapling
weak
fmradiords.com
31.220.20.22
443
ok
Tls12

ECDH Ephermal
256
Aes128
128
Sha1
error checking OCSP stapling
weak
Chain (complete)
1CN=fmradiords.com

2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
www.fmradiords.com
31.220.20.22
443
ok
Tls12
ECDH Ephermal
256
Aes128
128
Sha1
error checking OCSP stapling
weak
www.fmradiords.com
31.220.20.22
443
ok
Tls12

ECDH Ephermal
256
Aes128
128
Sha1
error checking OCSP stapling
weak
Chain (complete)
1CN=fmradiords.com

2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


8. Certificates

1.
1.
CN=fmradiords.com
01.07.2019
29.09.2019
47 days expired
fmradiords.com, www.fmradiords.com - 2 entries
1.
1.
CN=fmradiords.com
01.07.2019

29.09.2019
47 days expired
fmradiords.com, www.fmradiords.com - 2 entries

KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:038A32FCB5206DF321E2B7BF8914AFACFFED
Thumbprint:83DE052D7F946D1DB8909565FC1CF8FD12F200B4
SHA256 / Certificate:+Ds4xSKJDGASxOcRfRK/PBi7nY9CBalt7z31w3nfB10=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):2bfd896590f3f4daa4146f49c057e77186fb40b603f0bc321d3ae2d03070cd7f
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
expires in 488 days


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
expires in 488 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
expires in 685 days


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
expires in 685 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no



9. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
995778295
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-01 18:00:52
2019-09-29 18:00:52
fmradiords.com, www.fmradiords.com - 2 entries



2. Source crt.sh - old and new certificates, sometimes very slow.

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1631259159
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-01 16:00:52
2019-09-29 16:00:52
fmradiords.com, www.fmradiords.com
2 entries



10. Html-Content - Entries

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


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.fmradiords.com



1
0
fmradiords.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
fmradiords.com

ok
1
0
www.fmradiords.com


1
0
_acme-challenge.fmradiords.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.fmradiords.com

Name Error - The domain name does not exist
1
0
_acme-challenge.fmradiords.com.fmradiords.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.fmradiords.com.fmradiords.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.fmradiords.com.www.fmradiords.com

Name Error - The domain name does not exist
1
0


13. Portchecks (BETA)

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.



Permalink: https://check-your-website.server-daten.de/?i=fe3c88b2-5b8f-466a-9f6e-55c08729a61e


Last Result: https://check-your-website.server-daten.de/?q=fmradiords.com - 2019-07-02 16:00:44


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

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