Alternatives to ing.net
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
ing.net was registered with whois.verisign-grs.com on 25 Sept 1999. 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 ing.net. Refresh the analysis to check again.
835 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| inq.inc | Look-alike characters | 14 Nov 2026 | Checking… | Report → |
| irig.pro | Look-alike characters | 14 Nov 2026 | Checking… | Report → |
| inq.nexus | Look-alike characters | 13 Nov 2026 | Checking… | Report → |
| inq.digital | Look-alike characters | 12 Nov 2026 | Checking… | Report → |
| inq.be | Look-alike characters | 8 Nov 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is ing.net’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Netherlands | 51.6% | 85,924 | 87.6% | 12.4% |
| Spain | 22.6% | 37,650 | 100% | 0% |
| India | 13.2% | 21,894 | 100% | 0% |
| United Kingdom | 5.2% | 8,651 | 100% | 0% |
| Belgium | 3.9% | 6,536 | 100% | 0% |
| Host | Name server | TTL |
|---|---|---|
| ing.net | eur2.akam.net | 3599 |
| ing.net | eur6.akam.net | 3599 |
| ing.net | ns1-229.akam.net | 3599 |
| ing.net | ns1-34.akam.net | 3599 |
| ing.net | usc4.akam.net | 3599 |
| ing.net | use9.akam.net | 3599 |
| ing.net | usw1.akam.net | 3599 |
| ing.net | usw2.akam.net | 3599 |
| Host | Text | TTL |
|---|---|---|
| ing.net | "google-site-verification=1kGLMgs4OQpD-zPNaj8bAWcEpckMkXRMOPahvjQL6UY" | 3600 |
| ing.net | "identrust_validate=zyb46b2rgjAhCfR+ztMT6CELGmYnADwqmIMvm1eTAh6w" | 3600 |
| ing.net | "MS=ms52133147" | 3600 |
| ing.net | "v=spf1 include:_spf.ing.net -all" | 3600 |
| Host | Policy | TTL |
|---|---|---|
| ing.net | 0 iodef mailto:ing.certificate.management@ing.nl | 3600 |
| ing.net | 128 issue entrust.net | 3600 |
| ing.net | 128 issue identrust.com | 3600 |
| ing.net | 128 issuewild entrust.net | 3600 |
| ing.net | 128 issuewild identrust.com | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| ing.net | eur6.akam.net postmaster.mail.ing.nl 2007044350 14400 3600 604800 3600 | 3600 |
No reviews yet. Used ing.net? 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.
ing.net has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
ing.net is registered through whois.verisign-grs.com. See WHOIS →
The registration expired on 25 Sept 2024. See Overview →
ing.net was registered on 25 Sept 1999, making it 27 years old. See Overview →
Raw registry data for ing.net. May be redacted by privacy services.
{"objectClassName":"domain","handle":"10656290_DOMAIN_NET-VRSN","ldhName":"ING.NET","links":[{"value":"https:\/\/rdap.verisign.com\/net\/v1\/domain\/ING.NET","rel":"self","href":"https:\/\/rdap.verisign.com\/net\/v1\/domain\/ING.NET","type":"application\/rdap+json"},{"value":"https:\/\/apis.cscglobal.com\/dbs\/rdap-api\/v1\/domain\/ING.NET","rel":"related","href":"https:\/\/apis.cscglobal.com\/dbs\/rdap-api\/v1\/domain\/ING.NET","type":"application\/rdap+json"}],"status":["client transfer prohibited","server delete prohibited","server transfer prohibited","server update prohibited"],"entities":[{"objectClassName":"entity","handle":"299","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"299"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","CSC Corporate Domains, Inc."]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:8887802723"],["email",{},"text","domainabuse@cscglobal.com"]]]}]}],"events":[{"eventAction":"registration","eventDate":"1999-09-25T05:08:59Z"},{"eventAction":"expiration","eventDate":"2024-09-25T05:08:59Z"},{"eventAction":"last changed","eventDate":"2022-09-21T05:07:56Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-10-22T10:01:54Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"EUR2.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"EUR6.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"NS1-229.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"NS1-34.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"USC4.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"USE9.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"USW1.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"USW2.AKAM.NET"}],"rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_0","icann_rdap_response_profile_0"],"notices":[{"title":"Terms of Use","description":["Service subject to Terms of Use."],"links":[{"href":"https:\/\/www.verisign.com\/domain-names\/registration-data-access-protocol\/terms-service\/index.xhtml","type":"text\/html"}]},{"title":"Status Codes","description":["For more information on domain status codes, please visit https:\/\/icann.org\/epp"],"links":[{"href":"https:\/\/icann.org\/epp","type":"text\/html"}]},{"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https:\/\/icann.org\/wicf"],"links":[{"href":"https:\/\/icann.org\/wicf","type":"text\/html"}]}]}Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with ing.net. 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.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.