Alfacard.info - Alfa Card


updated on

www.alfacard.info website info

Homepage

Title: AlfaCard.info
URL: https://alfacard.info/

Other meta

  • generator: WordPress 5.5.3
  • viewport: width=device-width, initial-scale=1

Webserver

Signature: nginx
Response status code: 200
Response speed: 6209 milliseconds

HTTP headers

  • Connection: keep-alive
  • Content-Encoding: gzip
  • Content-Type: text/html; charset=UTF-8
  • Date: Wed, 11 Nov 2020 00:55:01 GMT
  • Link: <https://alfacard.info/wp-json/>; rel="https://api.w.org/", <https://alfacard.info/wp-json/wp/v2/pages/2>; rel="alternate"; type="application/json", <https://alfacard.info/>; rel=shortlink
  • Strict-Transport-Security: max-age=31536000;
  • Transfer-Encoding: chunked
  • Vary: Accept-Encoding
  • X-Pingback: https://alfacard.info/xmlrpc.php
  • X-Powered-By: PHP/7.3.6

Similar domains

updated on

DNS data

« DNS » (Domain Name System) is the phone book for the Internet. It converts human readable names like "alfacard.info" to a phone number so computers can call each other. Well, actually Internet uses IP Addresses, not phone numbers.

Apex

SOA

TTL: 3600
Serial number: 2020110902
Retry: 3600
Negative caching time: 86400
Primary master: server243.hosting.reg.ru.
Zone admin: support.reg.ru.
Refresh: 3600
Expire: 604800

NS

TTL: 3600
Servers: ns2.hosting.reg.ru and ns1.hosting.reg.ru

MX

TTL: 3600
Servers:

  • mx2.hosting.reg.ru - 20
  • mx1.hosting.reg.ru - 10

A

TTL: 3600
Canonical name: alfacard.info.
Address: 31.31.198.38

AAAA

TTL: 3600
Canonical name: alfacard.info.
Address: 2a00:f940:2:2:1:1:0:243


www.alfacard.info

A

TTL: 3600
Canonical name: www.alfacard.info.
Address: 31.31.198.38

AAAA

TTL: 3600
Canonical name: www.alfacard.info.
Address: 2a00:f940:2:2:1:1:0:243


alfacard.info live DNS

Check live dns records for alfacard.info on dnstoolkit.net

Timeline of events

  • 11/23/20: transferred from ns1.hosting.reg.ru. and ns2.hosting.reg.ru. to ns1.ukit.com., ns2.ukit.com., and ns3.ukit.com.
  • 11/9/20: registered on ns1.hosting.reg.ru. and ns2.hosting.reg.ru.
  • 5/2/19: expired (was on ns1.expired.reg.ru. and ns2.expired.reg.ru.)
  • 3/24/19: transferred from ns1.beget.com., ns1.beget.pro., and ns2.beget.com. to ns1.expired.reg.ru. and ns2.expired.reg.ru.
  • 6/19/18: transferred from ns1.beget.com., ns1.beget.pro., ns2.beget.com., and ns2.beget.pro. to ns1.beget.com., ns1.beget.pro., and ns2.beget.com.
  • 3/27/18: transferred from ns1.reg.ru. and ns2.reg.ru. to ns1.beget.com., ns1.beget.pro., ns2.beget.com., and ns2.beget.pro.
  • 3/24/18: registered on ns1.reg.ru. and ns2.reg.ru.
  • 11/14/17: expired (was on ns1.expired.reg.ru. and ns2.expired.reg.ru.)