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



U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
14.05.2022 16:50:19


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
api.next.flyver.ir

Name Error
yes
1
0
www.api.next.flyver.ir

Name Error
yes
1
0
*.next.flyver.ir
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.api.next.flyver.ir
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



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



1 RRSIG RR to validate DNSKEY RR found



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



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "ir" and the NextOwner "irish". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: NS, RRSIG, NSEC



0 DNSKEY RR found




Zone: flyver.ir
flyver.ir
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: next.flyver.ir
next.flyver.ir
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: api.next.flyver.ir
api.next.flyver.ir
0 DS RR in the parent zone found

Zone: www.api.next.flyver.ir
www.api.next.flyver.ir
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.api.next.flyver.ir
  b.ns.arvancdn.net

api.next.flyver.ir
  b.ns.arvancdn.net

next.flyver.ir
  b.ns.arvancdn.net
2a0c:a7c0:3::
Tehran/Iran (IR) - Noyan Abr Arvan Co. ( Private Joint Stock)

flyver.ir
  b.ns.arvancdn.net
2a0c:a7c0:3::
Tehran/Iran (IR) - Noyan Abr Arvan Co. ( Private Joint Stock)


  n.ns.arvancdn.com
2a0c:a7c0:2::
Tehran/Iran (IR) - Noyan Abr Arvan Co. ( Private Joint Stock)

ir
  a.nic.ir


  b.nic.ir / localhost


  dns-ir.univie.ac.at / dns-ir.univie.ac.at


  ir.cctld.authdns.ripe.net / ns1.nl-ams.authdns.ripe.net


  ns1.nic.ir


  ns5.univie.ac.at


4. SOA-Entries


Domain:ir
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:ir
Zone-Name:ir
Primary:ns1.nic.ir
Mail:info.nic.ir
Serial:2022051418
Refresh:14400
Retry:1800
Expire:604800
TTL:1440
num Entries:5


Domain:flyver.ir
Zone-Name:flyver.ir
Primary:b.ns.arvancdn.net
Mail:hostmaster.arvancloud.com
Serial:1652537545
Refresh:86400
Retry:7200
Expire:604800
TTL:7200
num Entries:2


Domain:next.flyver.ir
Zone-Name:flyver.ir
Primary:b.ns.arvancdn.net
Mail:hostmaster.arvancloud.com
Serial:1652537545
Refresh:86400
Retry:7200
Expire:604800
TTL:7200
num Entries:1


Domain:api.next.flyver.ir
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.api.next.flyver.ir
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 "api.next.flyver.ir" is subdomain, public suffix is ".ir", top-level-domain is ".ir", top-level-domain-type is "country-code", Country is Iran (Islamic Republic of), tld-manager is "Institute for Research in Fundamental Sciences", num .ir-domains preloaded: 214 (complete: 175327)
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

AInfo:: 8 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 8 Queries complete, 6 with IPv6, 2 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: b.ns.arvancdn.net, n.ns.arvancdn.com, 2 Name Servers included in Delegation: b.ns.arvancdn.net, n.ns.arvancdn.com, 2 Name Servers included in 1 Zone definitions: b.ns.arvancdn.net, n.ns.arvancdn.com, 1 Name Servers listed in SOA.Primary: b.ns.arvancdn.net.
AGood: Only one SOA.Primary Name Server found.: b.ns.arvancdn.net.
AGood: SOA.Primary Name Server included in the delegation set.: b.ns.arvancdn.net.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
A
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a0c:, 1 different subnets (first two blocks): 2a0c:a7c0:, 2 different subnets (first three blocks): 2a0c:a7c0:0002:, 2a0c:a7c0:0003:, 2 different subnets (first four blocks): 2a0c:a7c0:0002:0000:, 2a0c:a7c0:0003:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: b.ns.arvancdn.net: 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: b.ns.arvancdn.net: 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: ns1.nic.ir: 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.
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: 33057 milliseconds, 33.057 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)

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

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3726801183
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-05-14 06:39:46
2022-08-12 06:39:45
api.next.flyver.ir - 1 entries



2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
6726311107
precert
CN=R3, O=Let's Encrypt, C=US
2022-05-14 04:39:46
2022-08-12 04:39:45
api.next.flyver.ir
1 entries



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: b.ns.arvancdn.net, n.ns.arvancdn.com

QNr.DomainTypeNS used
1
net
NS
l.root-servers.net (2001:500:9f::42)

Answer: 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
2
b.ns.arvancdn.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.arvancdn.net, ns2.arvancdn.net

Answer: ns1.arvancdn.net
185.215.234.253

Answer: ns2.arvancdn.net
185.215.235.253
3
com
NS
l.root-servers.net (2001:500:9f::42)

Answer: 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
n.ns.arvancdn.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.arvancdn.com, ns2.arvancdn.com

Answer: ns1.arvancdn.com
185.215.234.253, 2a0c:a7c0:2::

Answer: ns2.arvancdn.com
185.215.235.253, 2a0c:a7c0:3::
5
b.ns.arvancdn.net: 185.215.235.253
A
ns1.arvancdn.net (185.215.234.253)
6
b.ns.arvancdn.net: 2a0c:a7c0:3::
AAAA
ns1.arvancdn.net (185.215.234.253)
7
n.ns.arvancdn.com: 185.215.235.253
A
ns1.arvancdn.com (2a0c:a7c0:2::)
8
n.ns.arvancdn.com: 2a0c:a7c0:2::
AAAA
ns1.arvancdn.com (2a0c:a7c0:2::)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
next.flyver.ir
0

no CAA entry found
1
0
flyver.ir
0

no CAA entry found
1
0
ir
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
next.flyver.ir

ok
1
0
_acme-challenge.api.next.flyver.ir.next.flyver.ir

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=2127be2a-6c0d-49b3-949c-8c512ac2b48a


Last Result: https://check-your-website.server-daten.de/?q=api.next.flyver.ir - 2022-05-14 16:50:19


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

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