Domain Intelligence Report
telegram.company
Gathering intelligence... (0/12)
DNS
WHOIS
Security
Email
DNSSEC
Threats
Deliverability
SSL/TLS
HTTP
Tech Stack
Subdomains
Archive
Safe
Checking…no attacks or spoofing
Up
Checking…reachable and responding
Right
Set up Page Watchit is what it is
Ready
Checking…you see what's coming
Outline
Gathering data — check results will appear here as they complete.
DNS Records
WHOIS
Then vs Nownew
No card for this name. We compare then and now for domains that are in the top million and had an AboutUs page. That says nothing about this domain’s age or safety.
Check what it is now →SSL/TLS
Security
Email Auth
DNSSEC
Tech Stack
HTTP / Headers
Threats
Zone census
Subdomains
Web Archive
Deliverability
IPv6
Not checked yet. aaaa.bot has no recent IPv6 result for telegram.company. Run the check on aaaa.bot →
Lineage
Our records: May 8, 2014 → Nov 3, 2026DNS at dns-redirect.com · 4 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
DNS provider
3 earlier
- HostGatorMay – Jun 2014
- bigrock.inDec 2015 – Mar 2016
- foundationapi.comMar – Apr 2016
- rayanegarco.comApr 2018
- Nameservers not resolvedAug 2026
- PorkbunAug – Sep 2026
- dns-redirect.comNOWSeen from Oct 2026
What changed
- Missing from the zone file, then back between Sep 8, 2026 and Oct 28, 2026Listed on 2026-09-08, missing from the next held snapshot, listed again on 2026-10-28. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to dns-redirect.com between Sep 8, 2026 and Oct 28, 2026curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com → ns1.dns-redirect.com, ns2.dns-redirect.com.
- Missing from the zone file, then back between Aug 5, 2026 and Aug 8, 2026Listed on 2026-08-05, missing from the next held snapshot, listed again on 2026-08-08. A registry hold also removes a name, so this is not proof it was dropped.
- Missing from the zone file, then back between Apr 7, 2016 and Apr 3, 2018Listed on 2016-04-07, missing from the next held snapshot, listed again on 2018-04-03. A registry hold also removes a name, so this is not proof it was dropped.
- DNS moved to rayanegarco.com between Apr 7, 2016 and Apr 3, 2018dns3.parkpage.foundationapi.com, dns4.parkpage.foundationapi.com → dns77.rayanegarco.com, dns78.rayanegarco.com.
- DNS moved to foundationapi.com between Mar 25, 2016 and Mar 26, 2016dns1.bigrock.in, dns2.bigrock.in, dns3.bigrock.in, dns4.bigrock.in → dns3.parkpage.foundationapi.com, dns4.parkpage.foundationapi.com.
- DNS moved to bigrock.in between Jun 5, 2014 and Dec 17, 2015ns6503.hostgator.com, ns6504.hostgator.com → dns1.bigrock.in, dns2.bigrock.in, dns3.bigrock.in, dns4.bigrock.in.
Solid bar: the stretch we observed that name. Dot: a single sighting. Dotted line: no record between sightings of the same name. Nothing is drawn between different names.
DNS provider, registry zone files: 232 .company zone-file snapshots held, 2014-05-08 to 2026-11-03.
Want to know when telegram.company changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.