Hostname
gmtnl.com
Last fetched
gmtnl.com resolves to 195.177.237.144, announced in 195.177.237.0/24 by CMS-VSMU-AS - National Pirogov Memorial Medical University, Vinnytsia in UA. gmtnl.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
IPv6 resolution
No AAAA record for gmtnl.com is recorded in WhisperGraph.
Attribution
national pirogov memorial medical university vinnytsia
ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of gmtnl.com owner
- Contact emails
- gmtnl.com@domainsbyproxy.com, 08caaf44-87d8-4ee7-a37b-282343d176be@identity-protect.org, 1f4a14fd-d37c-41b9-91f1-7e25785cb1c0@identity-protect.org, 2b0ebba6-c269-4afc-97cf-5db4bae7ca9e@identity-protect.org, 550efc79-9e1a-45f1-8c3a-78719d9d8a4f@identity-protect.org, 633a9851-b455-4b7e-929e-f99fce26b4a8@identity-protect.org, c1a5a738-169c-45ae-8750-4f424eae6791@identity-protect.org, f72fa213-f708-4f9d-92e6-ace30e184bab@identity-protect.org, owner-8913481@gmtnl.com.whoisprivacyservice.org
Subdomains
| Subdomain |
|---|
| backoffice-lts.gmtnl.com |
| bo-loadtest-lts.gmtnl.com |
| dgn-dbc-management.gmtnl.com |
| lts-aws-demo-app-ws-0.gmtnl.com |
| lts-aws-loadtest-app-public-1.gmtnl.com |
| lts-cdn-prod.gmtnl.com |
Showing 6 of 6 subdomains (6 per page).
Mail and authentication
Nameservers
- ns-198.awsdns-24.com
- ns-784.awsdns-34.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1073.awsdns-06.org
- ns-1978.awsdns-55.co.uk
Threat-feed evidence
History
Related pages
Pivot from gmtnl.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "gmtnl.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.