Skip to content

Hostname

upteambuilding.com

Last fetched

upteambuilding.com resolves to 185.158.113.99, announced in 185.158.112.0/23 by IPSERVER-RU-NET - IP Server LLC in RU. upteambuilding.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:51:26 GMT
Last seen on a feed
Sun, 13 Sep 2026 23:27:23 GMT

Nutrition Label

WHISPER CANON · upteambuilding.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/upteambuilding.com

Resolution chain

IPv6 resolution

No AAAA record for upteambuilding.com is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:1479
Registrant organisation
domain administrator
Contact emails
pw-2e10ffeedbaabc3568c4ef25dd5d6ac2@privacyguardian.org, pw-649c0048f4f976e60603fb24d58050c3@privacyguardian.org

Subdomains

Subdomain
mail.upteambuilding.com

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • upteambuilding.com
  • ns1.frienddns.info
  • ns2.frienddns.info
  • ns3.frienddns.net
  • ns4.frienddns.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

MX records

  • mail.upteambuilding.com

SPF policy

  • a: upteambuilding.com
  • mx: upteambuilding.com
  • ip: 185.158.113.99

Threat-feed evidence

History

Related pages

Pivot from upteambuilding.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: "upteambuilding.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.