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





1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
jammetti.lv

Name Error
yes
1
0
www.jammetti.lv

Name Error
yes
1
0


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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.12.2023, 00:00:00 +, Signature-Inception: 10.11.2023, 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: lv
lv
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 42018, DigestType 2 and Digest fpMqT5z5sc0EfCd+PNMjpT1CNH1Hx78d1gGP9LNE/Bw=



1 RRSIG RR to validate DS RR found



RRSIG-Owner lv., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.12.2023, 17:00:00 +, Signature-Inception: 18.11.2023, 16:00:00 +, KeyTag 46780, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 31113, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner lv., Algorithm: 8, 1 Labels, original TTL: 1800 sec, Signature-expiration: 26.11.2023, 00:20:38 +, Signature-Inception: 16.11.2023, 00:19:34 +, KeyTag 31113, Signer-Name: lv



RRSIG-Owner lv., Algorithm: 8, 1 Labels, original TTL: 1800 sec, Signature-expiration: 26.11.2023, 00:20:38 +, Signature-Inception: 16.11.2023, 00:19:34 +, KeyTag 42018, Signer-Name: lv



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



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



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

Zone: jammetti.lv
jammetti.lv
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 "1hh4f4sfkmg33l4ed2c4df0ut81ql85o" between the hashed NSEC3-owner "1hehgcp9juti8ror2sqkrqeisi4mbp4j" and the hashed NextOwner "1hjgva3h7ghoaasli1milrfm6u7kl5r8". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: TXT, RRSIG Validated: RRSIG-Owner 1hehgcp9juti8ror2sqkrqeisi4mbp4j.lv., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 28.11.2023, 16:21:09 +, Signature-Inception: 18.11.2023, 15:21:45 +, KeyTag 31113, Signer-Name: lv



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "98069sfth4ttnf008c49c783m75j5j7b" as Owner. That's the Hash of "lv" with the NextHashedOwnerName "981lbih44ee4affh9i63scq57cla7r3b". So that domain name is the Closest Encloser of "jammetti.lv". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 98069sfth4ttnf008c49c783m75j5j7b.lv., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 23.11.2023, 05:15:44 +, Signature-Inception: 13.11.2023, 05:07:00 +, KeyTag 31113, Signer-Name: lv



The ClosestEncloser says, that "*.lv" with the Hash "fqungsih6ds9fo9d1st74helqm4q11ae" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "fqukg2p0ejfevgqh8oddrn03rse0jbct" and the Next Owner "fr13s0rj1l2ud64n75d5qf3iq6j1rqro", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner fqukg2p0ejfevgqh8oddrn03rse0jbct.lv., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 26.11.2023, 10:27:38 +, Signature-Inception: 16.11.2023, 10:10:45 +, KeyTag 31113, Signer-Name: lv

Zone: www.jammetti.lv
www.jammetti.lv
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "98069sfth4ttnf008c49c783m75j5j7b" as Owner. That's the Hash of "lv" with the NextHashedOwnerName "981lbih44ee4affh9i63scq57cla7r3b". So that domain name is the Closest Encloser of "www.jammetti.lv". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 98069sfth4ttnf008c49c783m75j5j7b.lv., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 23.11.2023, 05:15:44 +, Signature-Inception: 13.11.2023, 05:07:00 +, KeyTag 31113, Signer-Name: lv



The ClosestEncloser says, that "*.lv" with the Hash "fqungsih6ds9fo9d1st74helqm4q11ae" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "fqukg2p0ejfevgqh8oddrn03rse0jbct" and the Next Owner "fr13s0rj1l2ud64n75d5qf3iq6j1rqro", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner fqukg2p0ejfevgqh8oddrn03rse0jbct.lv., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 26.11.2023, 10:27:38 +, Signature-Inception: 16.11.2023, 10:10:45 +, KeyTag 31113, Signer-Name: lv


3. Name Servers

DomainNameserverNS-IP
www.jammetti.lv
  a.nic.lv

jammetti.lv
  a.nic.lv

lv
  a.nic.lv / a-riga


  b.nic.lv / b-nic


  d.nic.lv / ac-daug


  n.nic.lv / s2.amx


  nu.nic.lv / u1.sub


  sunic.sunet.se


4. SOA-Entries


Domain:lv
Zone-Name:lv
Primary:a.nic.lv
Mail:dns.nic.lv
Serial:1700337004
Refresh:3600
Retry:900
Expire:1296000
TTL:1800
num Entries:6


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


Domain:www.jammetti.lv
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 "jammetti.lv" is domain, public suffix is ".lv", top-level-domain is ".lv", top-level-domain-type is "country-code", Country is Latvia, tld-manager is "University of Latvia Institute of Mathematics and Computer Science Department of Network Solutions (DNS)", num .lv-domains preloaded: 100 (complete: 231048)
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.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.jammetti.lv

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

A
A
AInfo:: 6 different Name Servers found: a.nic.lv, b.nic.lv, d.nic.lv, n.nic.lv, nu.nic.lv, sunic.sunet.se, 6 Name Servers included in Delegation: a.nic.lv, b.nic.lv, d.nic.lv, n.nic.lv, nu.nic.lv, sunic.sunet.se, 6 Name Servers included in 1 Zone definitions: a.nic.lv, b.nic.lv, d.nic.lv, n.nic.lv, nu.nic.lv, sunic.sunet.se, 1 Name Servers listed in SOA.Primary: a.nic.lv.
AGood: Only one SOA.Primary Name Server found.: a.nic.lv.
AGood: SOA.Primary Name Server included in the delegation set.: a.nic.lv.
AGood: All Name Server Domain Names have a Public Suffix.
A
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: a.nic.lv: 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: a.nic.lv: 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.

4. 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.
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: 80097 milliseconds, 80.097 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" > of the last months 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


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
lv
0

no CAA entry found
1
0


14. TXT - Entries

No TXT entries found


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=c792c280-3e44-4912-adcd-ae72de7bfede


Last Result: https://check-your-website.server-daten.de/?q=jammetti.lv - 2023-11-18 20:53: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=jammetti.lv" target="_blank">Check this Site: jammetti.lv</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro