amph.su was registered on 18 Sept 1990 and is hosted on AS198610 Beget LLC in Russian Federation. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed amph.su. Refresh the analysis to check again.
166 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| amph.me | Other extension | 19 Sept 2026 | Checking… | Report → |
| anph.shop | Typo | 6 Nov 2026 | Checking… | Report → |
| ampy.si | Typo | 8 Oct 2026 | Checking… | Report → |
| anph.dev | Typo | 6 Oct 2026 | Checking… | Report → |
| ampy.online | Typo | 28 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is amph.su’s name taken on other extensions?
Every IP address amph.su resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| amph.su | 5.101.159.26 | 300 |
| Host | Name server | TTL |
|---|---|---|
| amph.su | ns1.expired.beget.com | 300 |
| amph.su | ns2.expired.beget.com | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| amph.su | ns1.expired.beget.com hostmaster.beget.com 1747208437 300 600 86400 300 | 300 |
Other domains served from 5.101.159.26. Normal for shared hosting and CDNs.
No reviews yet. Used amph.su? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
amph.su has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
amph.su was registered on 18 Sept 1990, making it 36 years old. See Overview →
amph.su is served from 1 IP address, mainly on AS198610 Beget LLC in Russian Federation. See Hosting →
Raw registry data for amph.su. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.tcinet.ru domain: SU organisation: Russian Institute for Development of Public Networks organisation: (ROSNIIROS) address: 1, Kurchatov Sq. address: Moscow 123182 address: Russian Federation (the) contact: administrative name: ROSNIIROS organisation: Russian Institute for Development of Public Networks (ROSNIIROS) address: 1, Kurchatov Sq. address: Moscow 123182 address: Russian Federation (the) phone: +7 499 196 49 84 fax-no: +7 499 196 49 84 e-mail: [email protected] contact: technical name: Technical Center of Internet organisation: Technical Center of Internet address: 8 Marta street 1, bld 12 address: Moscow 127083 address: Russian Federation (the) phone: +7 495 730 29 69 fax-no: +7 495 730 29 68 e-mail: [email protected] nserver: A.DNS.RIPN.NET 193.232.128.6 2001:678:17:0:193:232:128:6 nserver: B.DNS.RIPN.NET 194.85.252.62 2001:678:16:0:194:85:252:62 nserver: D.DNS.RIPN.NET 194.190.124.17 2001:678:18:0:194:190:124:17 nserver: E.DNS.RIPN.NET 193.232.142.17 2001:678:15:0:193:232:142:17 nserver: F.DNS.RIPN.NET 193.232.156.17 2001:678:14:0:193:232:156:17 ds-rdata: 52180 8 2 6c71a8d6b0c8b8c40a853c38e247d53011d2b4662164f0e645b8274ce2cf7c5b whois: whois.tcinet.ru status: ACTIVE remarks: Registration information: created: 1990-09-19 changed: 2024-07-16 source: IANA
The first response from http://www.amph.su, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with amph.su. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
We couldn't find an IP address for amph.su's web or mail servers to check.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.