Domains Archives - EBRAND https://ebrand.com/blog/category/domains/ Boost and protect your brands. Mitigate risks, Optimize revenues. Thu, 30 Oct 2025 11:42:15 +0000 en-US hourly 1 https://wordpress.org/?v=6.6.4 https://ebrand.com/wp-content/uploads/2023/04/favicon.svg Domains Archives - EBRAND https://ebrand.com/blog/category/domains/ 32 32 Objection Handling: Fighting Unwanted .BRAND gTLDs https://ebrand.com/blog/objection-handling-a-brands-guide-to-contesting-unwanted-brand-gtlds/ Thu, 30 Oct 2025 11:41:32 +0000 https://ebrand.com/?p=52378 Key Takeaway: The next ICANN gTLD round requires brands to master objection handling to protect their trademarks. A proactive Legal Rights Objection (LRO) filed with WIPO is your primary defense against conflicting domain applications.  Even the biggest brands in the world miss opportunities when it comes to domains, even companies like Google and McDonald’s. As […]

The post Objection Handling: Fighting Unwanted .BRAND gTLDs appeared first on EBRAND.

]]>
.kt-callout { font-family: "Open Sans", Sans-serif; background:#E4E4E4; border-radius:12px; padding:1.2rem 1.3rem; margin:2rem 0; border:1px solid #dcdcdc; border-top:6px solid #BF0D3E; /* accent at top */ } .kt-callout__content h3 { margin:.1rem 0 .6rem; color:#BF0D3E; font-size:1rem; font-weight:700; letter-spacing:.3px; text-transform:uppercase; } .kt-callout__content p { margin:0; color:#222; line-height:1.65; font-size:.95rem; }

Key Takeaway:

The next ICANN gTLD round requires brands to master objection handling to protect their trademarks. A proactive Legal Rights Objection (LRO) filed with WIPO is your primary defense against conflicting domain applications. 

Even the biggest brands in the world miss opportunities when it comes to domains, even companies like Google and McDonald’s. As the internet expands, we’ve all got to be ready for the next digital land grab. ICANN’s next round of New Generic Top-Level Domains (gTLDs) is set to go live in April 2026, so a surge of applications will flood the system. For established brands, this presents a critical vulnerability: The risk is that a third party applies for and secures a gTLD that is identical or confusingly similar to your valuable trademark. In this high-stakes environment, brands must develop an objection handling strategy, to meet infringements as soon as they arise. Your ability to effectively contest an infringing application can determine whether you control your brand’s destiny online or lose it to a rival actor. 

This image of blind lady justice illustrates our discussion topic: Objection handling for ICANN's new domain registration phase.

Here, we’ll navigate the upcoming gTLD cycle, so you’re prepared for any eventuality. This guide delves into the specifics of the Legal Rights Objection (LRO), your primary mechanism for objection handling. We will also clarify the critical distinction between Community and Brand applications, to lay the foundations for your objection strategy. The WIPO are now a major player in ICANN’s processes so we’ll clarify their role, and explain what their involvement means for your brand. Finally, we will explore the proactive side of the equation, securing your own .BRAND domain. You can also learn more about the strategic benefits of a .BRAND and how to leverage it, right here.

Understanding Objections: The Core of Objection Handling

If a third party applies for a gTLD string that conflicts with your registered trademark, you do not have to stand by and let it happen. All sensible brands implement a monitoring system around their trademarks for infringing registrations, so why not use a similar strategy for domains, another crucially important asset for your ecommerce? ICANN’s New gTLD Program includes a defense mechanism known as the Legal Rights Objection (LRO). This pre-delegation objection process forms the basis of ICANN’s formal objection handling. It allows you to challenge the application before the new domain extension is approved and goes live. This proactive measure forms the most cost-effective and strategic approach to protecting your IP from DotBrand infringements. Beyond that, you can also try to limit possible negative effects after the DotBrand in question has been launched. 

Filing a successful LRO requires you to demonstrate that the potential use of the applied-for gTLD by the applicant would be likely to infringe upon your established legal rights. An independent panel will evaluate the objection based on several factors. These factors include the strength and recognition of your trademark, whether the applicant has any legitimate rights or affiliation with the string, the applicant’s intent in applying for the gTLD, and whether the proposed gTLD would impair the distinctiveness or reputation of your brand. Nothing is set in stone, but there are serious talks about having the application round on a permanent basis, so it’s worth establishing your strategies before the landscape develops. A well-documented objection, backed by robust evidence of your trademark’s reach and goodwill, forms the bedrock of a successful objection handling strategy against an infringing application. 

Strategic Objection Handling: Community vs. Brand Applications

Effective objection handling means understanding the distinction between a Community-based application and a Standard application for gTLDs. This distinction fundamentally shapes the way that you’ll present your arguments. 

A Community Application is filed by an organization representing a clearly delineated group or sector, with social or commercial interests. The applicant must provide evidence for the gTLD’s community support, and prove that gTLD benefits that specific group. Examples from the previous round include .BANK, for the banking community, and .ECO for green and environmentalist movements. These applications receive priority from ICANN, and enjoyed a smooth registration process. If two entities apply for the same string, a community application will prevail over a standard application, provided it meets all the criteria. 

This image of hikers silhouetted celebrating on a mountaintop illustrates our discussion topic: Objection handling for ICANN's new domain registration phase.

On the other hand, commercial entities file Standard or Brand Applications for a string that represents its brand, such as .APPLE or .GOOGLE. These cases require no evidence for representing or benefitting the broader community. With standard, .BRAND domains, organizations establish them to control a digital namespace and expand the company’s identity online. 

Your approach to objection handling must adapt to each type of application, now that you know the difference. If you are a brand and an organization applies for your brand name as a community gTLD, your objection would focus on the lack of a legitimate community nexus and the resulting consumer confusion. On the other hand, if another commercial entity applies for your brand name, your LRO argument centers squarely on trademark infringement and the absence of the applicant’s rights to the string. 

The Role of WIPO in Objection Handling: The Exclusive Arbiter

ICANN appointed the WIPO as the exclusive provider for resolving disputes their upcoming round of gTLD applications. As a UN agency, WIPO, or the World Intellectual Property Organization, work to establish an international IP system, making them the choice partner for ICANN’s requirements. 

ICANN selected WIPO due to its unparalleled expertise and two-decade-long track record in resolving domain name disputes through the Uniform Domain-Name Dispute-Resolution Policy (UDRP). WIPO maintains the institutional knowledge, the global panel of neutral legal experts, and the established procedures to handle the complex, high-stakes nature of gTLD objections fairly and efficiently. For brands, this means that any LRO you file will be adjudicated by a WIPO-appointed panel with deep experience in international trademark law and domain name conflicts. This provides a significant level of trust and predictability in the objection handling process. As WIPO itself states, it will publish detailed guidelines and resources as the next application round finalizes, making it essential for brands to monitor their updates closely. 

The .BRAND Imperative

Beyond playing defense, the new gTLD round is a call to action for brand offense. Securing your own .BRAND domain is a powerful move that renders defensive objection handling for that string unnecessary. In the last round, forward-thinking companies, from international retail chains to world-renowned auto firms, successfully navigated the application process. The benefits they unlocked are substantial. 

A .BRAND domain creates a secure and controlled digital ecosystem. It enhances brand authenticity, as every website under your .BRAND, from news.brand to careers.brand, is instantly verified and trusted by customers. These digital assets deliver powerful new marketing opportunities, allowing for concise, memorable URLs for specific campaigns. They also provide a definitive answer to cybersquatting at the top-level, eliminating the risk of yourbrand.sucks or other defensive registrations at the second level. 

However, the pioneers also revealed a common pitfall: a lack of imagination and follow-through. Some brands invested heavily in acquiring their .BRAND but failed to integrate it into their core digital strategy. The result was an underutilized asset, with the domain acting as a mere redirect to the existing .com site or, worse, lying completely dormant. The drawback is not in the concept of a .BRAND, but in the failure to leverage it. A .BRAND is not just a new address. It establishes a platform for innovation, enabling new technological opportunities like blockchain-based verification, personalized web spaces for customers, and a streamlined, secure internal network. As we discuss here, organizations can also use these assets as new and evolving revenue streams, which is worth considering too. 

This image of a stop and go pedal in a vehicle illustrates our discussion topic: Objection handling for ICANN's new domain registration phase.

Conclusions: Building Your gTLD Strategy

The upcoming ICANN new gTLD round presents a pivotal moment for brand owners. The landscape requires a dual strategy: You should prepare a vigilant defense of your trademarks through the WIPO-administered Legal Rights Objection process. Beyond that, an educated decision on whether to claim your own DotBrand domain reduces the risks associated to missed opportunities and challenges. The time to prepare your objection handling protocols is now, long before the anticipated application window in the second quarter of 2026. 

Do not let your brand become a case study in missed opportunity or costly dispute resolution. A unique DotBrand domain can be more than a web extension. It’s a gateway to plenty of digital opportunities, from brand-defining marketing campaigns to innovative blockchain capabilities. Of course, it’s not for everyone, but it’s worth exploring, so you can make a decision based on diligence and facts. 

Our team at EBRAND is expert in navigating the complexities of the ICANN application process. We provide comprehensive support, from developing a robust benefit analysis to the strategy to securing and strategically implementing your .BRAND. We help you not only to acquire your digital asset but to build a visionary plan for its use. Contact us below to schedule a consultation and discover how you can actively define your brand’s future on the internet. 

The post Objection Handling: Fighting Unwanted .BRAND gTLDs appeared first on EBRAND.

]]>
TLS vs SSL Certificates – How Are They Different https://ebrand.com/blog/tls-vs-ssl-certificates-how-are-they-different/ Mon, 27 Oct 2025 16:29:52 +0000 https://ebrand.com/?p=52016 Key Takeaway: TLS is the modern, secure protocol that replaced SSL, which is now deprecated due to known vulnerabilities. Although still called “SSL certificates,” all current certificates operate using TLS. The key difference lies in protocol versions, encryption strength, handshake process, and ongoing support – TLS 1.2 and TLS 1.3 are the recommended standards for […]

The post TLS vs SSL Certificates – How Are They Different appeared first on EBRAND.

]]>
.kt-callout { font-family: "Open Sans", Sans-serif; background:#E4E4E4; border-radius:12px; padding:1.2rem 1.3rem; margin:2rem 0; border:1px solid #dcdcdc; border-top:6px solid #BF0D3E; /* accent at top */ } .kt-callout__content h3 { margin:.1rem 0 .6rem; color:#BF0D3E; font-size:1rem; font-weight:700; letter-spacing:.3px; text-transform:uppercase; } .kt-callout__content p { margin:0; color:#222; line-height:1.65; font-size:.95rem; }

Key Takeaway:

TLS is the modern, secure protocol that replaced SSL, which is now deprecated due to known vulnerabilities. Although still called “SSL certificates,” all current certificates operate using TLS. The key difference lies in protocol versions, encryption strength, handshake process, and ongoing support – TLS 1.2 and TLS 1.3 are the recommended standards for secure communication.

Online security relies on cryptographic protocols, and while most websites claim to use an SSL certificate, it’s actually TLS that does the work. If your brand relies on secure communication, your team must know the difference between SSL and TLS as a top priority.

To help you safeguard your brand’s online presence, we at EBRAND offer a free brand audit that maps your digital footprint and flags impersonation or phishing threats.

The Evolution from SSL to TLS

The Evolution from SSL to TLS

The Secure Sockets Layer (SSL) protocol was originally developed to encrypt communication between web browsers and servers. SSL 2.0, released in 1995, was the first widely used version, but it contained significant vulnerabilities. Version 3.0 addressed many of these issues, but was eventually found to be insecure as well. Both SSL 2.0 and 3.0 are now deprecated.

Transport Layer Security (TLS) was introduced as the successor to SSL. TLS 1.0, released in 1999, retained the core architecture of SSL but improved its encryption capabilities. TLS 1.1, 1.2, and 1.3 have continued to refine the protocol, making it faster, more secure, and more adaptable to modern cryptographic requirements. Today, it is the modern standard for encrypted communication.

Technical Differences

While TLS and SSL are both cryptographic protocols that encrypt data between a server and a web browser, their technical foundations differ significantly. TLS supports newer, more secure encryption algorithms, including AEAD ciphers and modern elliptic curve cryptography. SSL relies on outdated algorithms that no longer meet today’s security standards.

Another major difference between TLS and SSL lies in the handshake process. The SSL handshake is slower, less flexible, and more vulnerable to downgrade attacks. TLS uses a more efficient handshake process, especially from version 1.2 onwards, supporting features such as forward secrecy and session resumption. TLS also provides stronger authentication methods and certificate validation mechanisms.

Both protocols use digital certificates issued by certificate authorities to authenticate the server and establish a secure connection. However, TLS certificates benefit from better algorithm support, better cipher suite negotiation, and more secure key exchange methods.

Here’s a side-by-side comparison to summarize the core differences between SSL and TLS:

FeatureSSL ( 2.0 / 3.0)TLS (1.0–1.3)
Encryption AlgorithmsOutdated and vulnerableModern and secure (e.g., AES, ChaCha20)
Handshake ProcessSlower, vulnerable to attacksFaster, supports forward secrecy
Certificate SupportBasic digital certificate validationStronger authentication and algorithms
Protocol FlexibilityLimited cipher suite negotiationRobust negotiation and fallback options
Security StatusDeprecated, no longer supportedActively maintained and recommended
Browser/Server SupportDisabled by most modern systemsFully supported by modern systems
Versions AvailableSSL 2.0, SSL 3.0TLS 1.0, 1.1, 1.2, 1.3
Usage in CertificatesLegacy term still usedActual protocol behind today’s certificates

Why the Term ‘SSL Certificate’ Is Still Used

Even though TLS is the protocol in use today, the term “SSL certificate” remains widely used in marketing and technical documentation. This leads to confusion for many users who assume they are installing an SSL certificate that uses the SSL protocol.

In reality, when you install a Secure Sockets Layer certificate today, whether a wildcard or a domain-specific certificate, it’s TLS that handles the secure communication. The certificate still performs the same function: it authenticates the server and enables encryption, but under the TLS protocol. Most SSL certificates and TLS certificates are essentially the same in function, but “SSL” persists as a legacy naming convention.

How SSL and TLS Work in Practice

Both SSL and TLS protocols enable secure connections using a multi-step process that involves server authentication, encryption setup, and secure data transmission. During the handshake process, the server presents its digital certificate to the client, which is verified using the public key infrastructure and trusted certificate authorities.

If authentication is successful, a shared session key is negotiated using a cryptographic algorithm, which then encrypts all communication between the client and the server. While the SSL handshake used to perform this role, the TLS handshake process has replaced it in modern secure communication.

TLS 1.2 and 1.3 also support newer cryptographic algorithms and remove outdated features that made earlier SSL versions vulnerable. TLS is used in HTTPS-based secure communication, email encryption, and other protocols, while SSL is no longer considered safe for any type of transmission.

Security and Compatibility: SSL Deprecation vs TLS Adoption

SSL is now considered obsolete. SSL 2.0 and 3.0 are officially deprecated, and most major web browsers and servers have disabled support for them. TLS 1.0 and 1.1 were also formally deprecated, but some legacy systems still support them. The recommended standards are TLS 1.2 and 1.3, which offer better encryption, shorter handshakes, and improved security.

TLS is the updated version of SSL in every functional sense. It supports modern authentication, robust encryption, and flexible protocol negotiation. Today’s secure certificates work over the TLS protocol by default. In fact, the SSL certificates that EBRAND issues with our clients all come with TLS encryption by default. Ultimately, TLS is the protocol that enables HTTPS encryption across the web.

TLS Certificates and Certificate Management

Modern TLS Certificates and Certificate Management

Although the term “SSL certificate” still appears in dashboards, control panels, and product names, all certificates in use today rely on TLS. Whether you use a standard or wildcard Secure Sockets Layer certificate, the underlying encryption occurs via the TLS protocol.

Certificate management involves acquiring a certificate from a trusted certificate authority, installing it on your server, and ensuring timely renewals, particularly as industry standards regarding SSL certificate lifespans evolve. Implementing TLS also means staying current with the latest TLS version and disabling insecure versions of SSL or TLS.

When you install an SSL certificate today, you’re really implementing TLS encryption, because TLS is the cryptographic protocol that encrypts data, authenticates the server, and ensures secure communication.

Conclusion

The key differences between TLS and SSL lie in security, protocol design, and long-term viability. While SSL once set the standard for encrypted connections, its vulnerabilities led to deprecation. Today, its successor is not just more secure, but actively maintained and widely supported.

Despite the continued use of the term “SSL certificate,” it’s the newer protocol that handles encrypted communication across the web. If your systems still rely on outdated technology or ambiguous configurations, upgrading to the latest version is critical. Legacy methods no longer offer adequate protection; modern certificate deployment should be built entirely on current, secure protocols.

The post TLS vs SSL Certificates – How Are They Different appeared first on EBRAND.

]]>
NIS2: What Your Business Needs to Know About Compliance  https://ebrand.com/blog/nis2-what-your-business-needs-to-know-about-compliance/ Thu, 28 Aug 2025 09:19:13 +0000 https://ebrand.com/?p=51240 Key Takeaway: NIS2 redefines domain regulations across Europe and beyond, shaping online infrastructure, cybersecurity, and digital verification. Businesses must act now to strengthen their domain management or risk losing their infrastructure altogether. Maintaining Compliance in a New Legislative Landscape The EU’s Network and Information Security Directive (NIS2) represents a major step forwards in digital security regulations. The […]

The post NIS2: What Your Business Needs to Know About Compliance  appeared first on EBRAND.

]]>

Key Takeaway:

NIS2 redefines domain regulations across Europe and beyond, shaping online infrastructure, cybersecurity, and digital verification. Businesses must act now to strengthen their domain management or risk losing their infrastructure altogether.

Maintaining Compliance in a New Legislative Landscape

The EU’s Network and Information Security Directive (NIS2) represents a major step forwards in digital security regulations. The directive expands the scope of its legislative predecessor, introducing stricter risk management, reporting obligations, and verification requirements. 

This image of a European Parliament building illustrates our discussion topic: NIS2, the changes for your organization, and the relevance of Corporate Domain Management.

Unlike older frameworks, NIS2 doesn’t just apply to critical infrastructure. Its reach now extends to industries like energy, healthcare, transport, cloud services, digital platforms, and beyond. Companies must tighten control over their online assets and adopt structured, proactive approaches to cybersecurity and operational resilience. 

For companies operating in the EU, NIS2 does not simply suggest these changes: Authorities will enforce them. Under the new regulation, organizations face financial penalties, legal consequences, and reputational harm if they fail to comply. They can ultimately lose their domain registration and access to their assets. 

Why Accurate WHOIS Data Matters Under NIS2 

While WHOIS details were always important, this directive makes them crucial for your operational continuity. Domain registrants must ensure that each and every domain under their control carries verified, up-to-date contact information. This information must include authentic email addresses, valid phone numbers, and correct organizational details.  

Failure to comply means serious consequences. Authorities can and will suspend domains with incomplete or incorrect WHOIS data. Organizations that fail to verify their registrant information face regulatory penalties, and operational disruption. Under NIS2, businesses cannot afford errors or inconsistencies in their registration details. For future-proof organizations with an effective online presence in Europe, NIS2 represents a necessity, not an option.  

NIS2 in the Wider Legislative Context 

This directive arrives at a time of growing regulatory pressure across Europe. In the EU, legislation like the Digital Operational Resilience Act (DORA) also reshapes standards for financial institutions. While DORA focuses primarily on operational continuity in the financial sector, its introduction signals a broader trend. European regulators expect businesses to adopt stricter cybersecurity measures and demonstrate stronger control over their digital infrastructure. 


This image of colleagues working at a computer bank illustrates our discussion topic: NIS2, the changes for your organization, and the relevance of Corporate Domain Management.

For most organizations, however, NIS2 remains the directive with the greatest immediate impact. It demands readiness across every aspect of online asset management and requires businesses to establish robust processes to avoid both operational and reputational risks. For a clearer focus on what DORA means for you, read our dedicated right here

Why Domain Management Is Central to NIS2 Compliance 

NIS2 places new responsibility on businesses to manage their online portfolios with precision. This means maintaining complete oversight of domains, certificates, DNS records, and registrant details while ensuring that all associated data remains accurate and verified. Without a clear, centralized process for managing these assets, businesses leave themselves open to compliance failures, cyberattacks, and operational disruptions. 

A comprehensive domain management platform like COSMOS helps organizations meet these obligations with ease. The platform supports corporate enterprises with international portfolios, delivering the tools to maintain control an evolving domain landscape. By consolidating control of your digital infrastructure, automating renewals, streamlining registrant verification, and providing full visibility across your portfolio, COSMOS ensures that nothing is overlooked. With NIS2 enforcing higher standards, solutions like COSMOS make it possible to stay compliant while reducing the risks associated with manual processes and outdated systems. 

We’ve designed the platform with specific features to meet the challenge. COSMOS streamlines asset management, automates renewals, and improves visibility across your digital infrastructure. You can answer compliance concerns, meet NIS2 obligations, and future-proof your infrastructure all in one place. 


This image of two people shaking hands in front of the EU flag illustrates our discussion topic: NIS2, the changes for your organization, and the relevance of Corporate Domain Management.

Conclusions: Securing Your Future Under NIS2 

NIS2 demands a new approach to cybersecurity, digital asset management, and infrastructural control. The directive raises the stakes for organizations across Europe, enforcing stronger processes, accurate WHOIS data, and robust management across your online portfolio. 

Now is the time to assess your infrastructure, review your domain portfolios, and implement compliance strategies. By addressing NIS2 requirements early and ensuring your registrant data stays accurate and verified, your business can reduce risks, strengthen defences, and position itself for long-term resilience in an increasingly regulated environment. 

Start by assessing your online infrastructure and uncovering potential gaps. Get your free domain management audit today and take the first step toward a safer, more compliant future. 

The post NIS2: What Your Business Needs to Know About Compliance  appeared first on EBRAND.

]]>
Are .su Websites Safe? https://ebrand.com/blog/are-su-websites-safe/ Tue, 29 Jul 2025 15:20:34 +0000 https://ebrand.com/?p=50130 Summary: The rise in scams, high-profile cyberattacks, and enforcement issues surrounding .su websites makes them a persistent threat for modern organizations. Sanctions and registration challenges make them harder to register and enforce against, but Corporate Domain Management helps monitor and mitigate risks associated with these Soviet-era domains.   Are scammers impersonating you on .su websites? […]

The post Are .su Websites Safe? appeared first on EBRAND.

]]>
Summary: The rise in scams, high-profile cyberattacks, and enforcement issues surrounding .su websites makes them a persistent threat for modern organizations. Sanctions and registration challenges make them harder to register and enforce against, but Corporate Domain Management helps monitor and mitigate risks associated with these Soviet-era domains.  

Are scammers impersonating you on .su websites? Find out now with a free domain scan

What does .su mean? 

International brands often use country-code top-level domains (ccTLDs) like .co.uk or .ca, or newer generic TLDs like .fast and .shop, to protect their online presence and expand into new markets. As luck would have it, cybercriminals exploit both channels. Impersonators and phishing attackers leverage new and existing domain extensions to spoof organizations and trick their innocent visitors. Among these, the .su domain stands out as a relic of the Soviet Union that still lingers in cyberspace, posing unique risks to brand integrity.  

This image of a chess player in Soviet-style dress illustrates our discussion topic: .su websites, their relevance to your domain cyberthreat landscape, and strategies for protecting yourself and your team.

High-profile threats linked to .su websites range from breach data forums to sophisticated phishing campaigns, all the way down to websites impersonating the target’s commercial business.. In this guide, we dissect the nuances of these dangers and outline strategies to combat them effectively.  

What are .su domains?

Authorities originally assigned the .su domain to the Soviet Union in 1990, just before its dissolution. Despite the USSR’s collapse just a year later, the domain remained active, managed by the Russian Institute for Development of Public Networks. Today, geopolitical tensions, particularly the Russia-Ukraine conflict and resulting sanctions, have made .su domains harder to register and even harder to enforce against.  

Andre Stadelmaier, our Senior Director of Sales and resident domain expert, notes that: “.su websites certainly are a worry for modern organizations. At the moment, they are more difficult to register for clients due to the international sanctions. Enforcement and takedowns would usually be advisable from a defensive perspective. Unfortunately, enforcing against them is certainly less successful compared with our usual enforcement work.”  

As Andre outlines, the difficulty registering .su domains make it harder for new scammers to exploit. However, the legacy of existing impersonations and malicious domains across the online landscape makes .su a lingering concern. Their historical ties and limited regulatory oversight pose all kinds of threats to organizations around the world. 

Threats from .su Websites 

According to a report from The Guardian, scams linked to .su domains doubled in recent years, even surpassing .ru and other Cyrillic domains in malicious activity. One of the most infamous cases involved Exposed.su, a site that allegedly leaked sensitive credit records of high-profile figures, including Michelle Obama, Mitt Romney, Donald Trump, and celebrities like Britney Spears, Jay-Z, Beyoncé, and Tiger Woods.  

Konrad Dudzinski, our Chief Intellectual Property Officer, adds that “.su domains have been one of the most problematic extensions, with lots of scams. New registrations for .su websites should already be blocked, yet I see that the domain is still active, at least for the next five years.”   

This image of a Cyrillic typewriter illustrates our discussion topic: .su websites, their relevance to your domain cyberthreat landscape, and strategies for protecting yourself and your team.

Despite ICANN’s plans to retire the .su domain by 2030, its current availability means organizations must remain vigilant against potential misuse.  

What Can We Do About .su Websites? 

Manually searching for your brand name alongside the .su extension may uncover some impersonations worth looking into. That being said, this method won’t uncover every threat online. Breach data may lurk under URLs unrelated to your brand, and scammers use subdomains to evade your searches. Even if you do uncover some malicious .su websites yourself, taking any action about them poses its own challenges. Already slow reporting and mitigation mechanisms slow to a halt in the face of international sanctions. However, more comprehensive and automated domain tools often yield better results. 

This is where Corporate Domain Management comes in. Advanced monitoring solutions can detect domain impersonations, typosquatting, and even unrelated URLs hosting malicious content. Real-time tracking of changes, such as newly added mail servers or payment systems, helps identify threats before they escalate. Enforcement actions, including cease-and-desist notices and UDRP complaints, may not always yield immediate results with .su domains, but they provide valuable insights and strengthen defensive strategies across all suspicious extensions, ccTLDs, and beyond.  

Conclusions: What’s Next? 

Clearly, .su websites remain a niche but persistent threat, shaped by historical legacy and geopolitical complexities. With the .su extension’s retirement at least five years over the horizon, organizations must stay proactive in monitoring and mitigating risks across all domain extensions.  

This image of a Soviet-era statue illustrates our discussion topic: .su websites, their relevance to your domain cyberthreat landscape, and strategies for protecting yourself and your team.

For further insights into dangerous ccTLDs, explore our blog on the Top Ten Most Risky Country-Code Domains. Understanding the nuances of domain monitoring and enforcement is critical in today’s digital landscape, where discovering and tracking malicious content can mean the difference between security and compromise.  

Want to make the most of your insights about .su domains? Get a free domain audit today and safeguard your brand against emerging threats. 

The post Are .su Websites Safe? appeared first on EBRAND.

]]>
Domain squatting: Expensive lapses vs proactive portfolios https://ebrand.com/blog/domain-squatting/ Thu, 24 Jul 2025 10:24:18 +0000 https://ebrand.com/?p=50005 What have search engines, football clubs, and the royal families all got in common? Not much, except they’ve all been the victims of domain squatting. And they’re not alone. Opportunists and cyberscammers shadow brands, organizations, and prominent figures, exploiting their digital footprints and registering lucrative domains. Whether they’re leveraging these assets to get a big […]

The post Domain squatting: Expensive lapses vs proactive portfolios appeared first on EBRAND.

]]>
What have search engines, football clubs, and the royal families all got in common? Not much, except they’ve all been the victims of domain squatting. And they’re not alone. Opportunists and cyberscammers shadow brands, organizations, and prominent figures, exploiting their digital footprints and registering lucrative domains. Whether they’re leveraging these assets to get a big payout, or actively running phishing and impersonation campaigns, domain squatting means trouble. 

This image of a derelict house covered in graffiti and a sign saying "no trespassing, keep out" illustrates our discussion topic: Domain squatting, its impact, and anti-squatting solutions for organizations and individuals.

In this guide, we’ll tackle the topic from top to bottom. We’ll examine the infrastructural foundations of domain registry and squatting, and learn from notable cases, resolved and otherwise. Exploring the history of domain squatting helps you prepare for your digital strategies in the future, as we conclude with solutions for squat-proofing your portfolio. You can also get started with a free domain squatting check right here, to see who’s lurking around your online assets. 

Defining domain squatting 

Domain squatting means registering infringing web addresses and related assets. In a more malicious sense than property squatting, cyber squatters anticipate things like product launches or brand expansions to scoop up tactically important domains, subdomains, and extensions, predicting their value for legitimate organizations and standing in the way. As you don’t always have to own a trademark or intellectual property before registering a domain, anyone can do it at any time, as long as it’s available. Some domain squatters even monitor trademark houses, and snap up domains as soon as a new registry appears. 

Obviously, domain squatting represents a murky grey area, where it’s perfectly legal in the tumultuous free market of our digital landscape. On one side of the spectrum, you have innocent entrepreneurs who buy a website in their home country, not knowing that an ambitious brand in another part of the world has their eye on it. On the other side of the spectrum, you have cybercriminal gangs, cybersquatting and typosquatting governments and banks to launch phishing attacks and finance scams against the most vulnerable in society. You also have opportunists who notice when existing domain registrations expire and jump in before anyone else notices. As we’ll see, domain squatting in all its forms affects businesses across industries, from SMEs to the largest corporations on the planet. 

How it affects businesses 

As mentioned above, domain squatting even struck Google, showing that no one is safe from losing their domains. A former employee owned the domain for around 60 seconds in 2016 when he noticed that the domain registration lapsed. Remarkably, a similar thing happened again five years later. An Argentinian man paid as little as $2.50 for the search engine’s .com.ar extension when it missed renewal in 2021. After he noticed that their website shut down following the domain’s registry expiration, he purchased it legally online. Google managed to resolve both cases quickly and cheaply, but you can imagine the existential struggles that a business with fewer resources might face. 

For example, while Liverpool Football Club succeeded in the Premier League in 2025, they still face setbacks when it comes to domains. The club’s representatives actually lost a domain dispute resolution case for the website liverpoolfctickets .com, an address that contains their organization name and a potential source of ecommerce revenue. Czech arbitration panellists ruled against them when they attempted to claim the domain, and it still remains a parking page at the time of writing. 
 
Plenty of businesses earn their reputation and their living on key domains. In many cases, detecting and eliminating cybersquatters makes the difference between growth and losses, between success and disaster. 

This top-down image of blocks of squats and shanty towns illustrates our discussion topic: Domain squatting, its impact, and anti-squatting solutions for organizations and individuals.

Organizations and authorities face domain squatting 

Beyond the private sector, non-profit groups and even governments face domain impersonations and lapses too. Hundreds of thousands of citizens in Northern Ireland received communications that included a weblink related to their property taxes, in April this year. Unfortunately, this link led to a website that was not owned by the Northern Irish government. According to cybersecurity academics, the link led to a cybersquatting page that attempted to download malware. 

Victims suffer when digital squatters exploit public trust in governments and authorities. In the private and public sectors alike, we have a duty to stay vigilant. Domain monitoring and digital squatting enforcement tactics help us keep organizations safe, along with the people who rely on them online. 

When celebrities and business leaders suffer domain squatting 

Crucially, it’s not just organizations that face domain infringements and digital crises. Cybersquatters and opportunists nab assets from CEOs, executives, athletes, actors, and anyone in the public eye. They often hold relevant and high-traffic domains to ransom, or use them for further schemes. Cybercriminal tactics involve fake promotion schemes, typically job scams or crypto, or generally using the domain’s mail servers for phishing attacks. 

While VIPs and executives face the majority of squatting attacks, opportunists even target babies. According to the BBC, domain names mentioning the name “George” rose by ten percent in the wake of the British Prince’s birth. One prince-related-domain holder put their asset on £10,000. This headline-grabbing story illustrates a broader problem that affects business leaders and VIPs around the world. As proactive prevention proves far more cost-effective than reclaiming a squatted domain, many fight back with tools like VIP and Executive Protection. 

Strategies for fighting back 

When it comes to eliminating domain squatting, there’s clearly no bullet-proof solution – even Google has its issues! That being said, implementing a few best practice principles help you minimize your risk and maximise your opportunities. 

Staying clear on your domain strategy limits the room for domain squatters to intercede. When you align product launches, trademark registrations, and domain portfolio expansion at the right times, you’ll streamline your budget and minimize worry, saving your team time and effort. 

This image of a key unlocking a door illustrates our discussion topic: Domain squatting, its impact, and anti-squatting solutions for organizations and individuals.

However, the problem is, domain squatting might already be an issue plaguing your brand as you read this. Manual detection and enforcement actions work fairly well for individuals and small businesses looking to secure their online landscape. Simply Googling for infringements and email domain hosts about the results can help. However, for SMEs and enterprises, Corporate Domain Management delivers effective solutions for detecting and eliminating domain squatting at scale.  

Conclusions: Your next steps 

To summarize, domain squatting can affect anyone and everyone. From Royal Princes in the UK, to global corporations like Google, everyone suffers from disputes on their online landscape.  

Knowing the scale of the problem delivers the best route towards solving your issues. Make the most of your insights, and get started with a free domain squatting audit right here.

The post Domain squatting: Expensive lapses vs proactive portfolios appeared first on EBRAND.

]]>
gTLD Applications: Unpacking ICANN’s Draft Applicant Guidebook https://ebrand.com/blog/gtld-applications-unpacking-icanns-draft-applicant-guidebook/ Wed, 25 Jun 2025 09:47:58 +0000 https://ebrand.com/?p=49797 As ICANN prepares to launch the long-awaited next round of new gTLD applications, the release of its Draft Applicant Guidebook (AGB) marks a pivotal milestone for brands, communities, and other prospective registry operators. The 2025 AGB outlines the process, fees, and policy updates shaping the next era of domain name expansion. Based on the June […]

The post gTLD Applications: Unpacking ICANN’s Draft Applicant Guidebook appeared first on EBRAND.

]]>
As ICANN prepares to launch the long-awaited next round of new gTLD applications, the release of its Draft Applicant Guidebook (AGB) marks a pivotal milestone for brands, communities, and other prospective registry operators. The 2025 AGB outlines the process, fees, and policy updates shaping the next era of domain name expansion.

This image of scrabble tiles spelling the word "guide" illustrates our discussion topic: New gTLD applications, and the latest from ICANN's draft applicants guidebook.

Based on the June 3 webinar hosted by ICANN, here’s what you need to know to confidently navigate the updated AGB. As you dive into the latest, below, you can also find out more about domain management and new gTLD strategies for your organization here.

A Refined Journey for gTLD Applications

The application process follows a clear path, starting with submission and prioritization, then moving through evaluation, resolving any conflicts, and ending with delegation. Along the way, there are important checkpoints, like checking for blocked names, geographic terms, name collisions, and similar strings.

ICANN will also assess applicants based on their financial and operational readiness, as well as the qualifications of their chosen registry service provider. Brand TLD applicants or those seeking a Code of Conduct exemption must meet extra requirements. Some evaluations, especially those related to geographic names or name collisions, can lead to longer reviews or challenges. That’s why planning ahead and paying close attention to the details is so important.

Key Differences from the 2012 Round

The 2025 AGB brings several important changes compared to the 2012 round. As an update from the previous briefing back in August, one of the biggest shifts covers private contention resolutions. The latest guidelines effectively ban private auctions and deals between applicants. Instead, ICANN will handle all conflicts through their official processing system. To help avoid early disputes, applicants can now submit a “Replacement String” within 14 days of Reveal Day. ICANN also introduced a new Predictability Framework to manage unexpected issues, with changes now classified as minor, non-minor, or policy-related. ICANN has added more detailed evaluation steps, stricter rules for geographic names, and a more transparent fee and refund system.

The guidelines also outline strict, legally binding enforcement procedures for new and existing commitments. These include Public Interest Commitments (PICs), Registry Voluntary Commitments (RVCs), and Community Registration Policies. Altogether, these updates aim to make the application process fairer, clearer, and more consistent.

gTLD Applications Fees and Refunds: What Have ICANN Changed?

The new applicant guidebook sets the base gTLD evaluation fee at $227,000. Applicants must pay within seven days of the application window closing. Withdrawals trigger a tiered refund schedule, starting at $147,550 and decreasing as evaluations progress.

Conditional evaluations incur additional fees, including:

  • Brand TLD eligibility: $500
  • Geographic name review: $18,000–$25,000
  • Name collision risk mitigation: $100,000–$150,000
  • Community Priority Evaluation: $50,000–$80,000

Applicants may be able to access volume and policy-based refunds in certain cases based on the new regulations. For example, in cases where the program changes significantly after application submission, or where high-risk strings get withdrawn, refunds may be on offer.

This image of someone opening boxes and ticking a to do list illustrates our discussion topic: New gTLD applications, and the latest from ICANN's draft applicants guidebook.

Community Input, Objections & Appeals

The AGB encourages multiple forms of stakeholder feedback. Application Comments, GAC Early Warnings, and Singular/Plural Notifications provide opportunities to flag issues that evaluators may consider. Formal objections  covering grounds such as string confusion, legal rights, public interest, or community concerns can potentially block or modify gTLD applications. These objections are handled by independent dispute resolution providers, and their determinations can be appealed.

Contention Sets: gTLD Applications Resolution Pathways

Contention happens when more than one applicant applies for the same or a similar string. In this round, the guidelines ban any kind of secretive deals to resolve these conflicts in private. Instead, applicants must settle disputes through either a Community Priority Evaluation (for eligible community applications) or an ICANN-run auction using a set bidding format.

To help avoid these situations, applicants can submit a “Replacement String” within 14 days after Reveal Day. This fallback option is designed to reduce contention early in the process. Applicants can list up to four alternative strings at the time of submission, allowing them to switch to one of them later, but only once. Once a switch is made, the applicant can’t go back to the original string, even if later contention arises with their new choice. Brand applicants may also request a Brand String Change, if they meet the required eligibility criteria.

Geographic Names: Strict Compliance Required

Applications for geographic gTLDs, such as names of cities or ISO-recognized regions, must be backed by formal support or non-objection from the relevant government or public authority. Without this documentation, the application will be denied. A specialized Geographic Names Panel (GNP) will evaluate all geographic applications to ensure the legitimacy of supporting documents and their alignment with the intended use of the string.

Registry Commitments & Public Interest

All applicants must include Public Interest Commitments (PICs) as part of their application. Beyond this, applicants may submit Registry Voluntary Commitments or, in the case of community-based TLDs, Community Registration Policies. These commitments are reviewed through a Registry Commitment Evaluation (RCE) to ensure that they are legally sound and can be included in the final registry agreement. Any provisions that imply content regulation will be rejected.

Predictability Framework: Structured Change Management

To address unforeseen changes, ICANN has introduced a Predictability Framework. This framework categorizes changes into minor, non-minor, and policy-level, depending on their impact on applicants and their alignment with existing policies. While minor changes can be implemented by ICANN alone, non-minor and policy-level changes require collaboration with community bodies such as SPIRT and the GNSO Council. Applicants will be notified of any non-minor changes, and a public change log will be maintained to ensure transparency.

What’s Next?

According to the current timeline, the final public comment period will close on July 23, 2025. ICANN will then finalize and publish the Applicant Guidebook no later than December 2025. The new gTLD applications round is expected to launch on the 30th of April 2026.

This image of someone launching a paper aeroplane illustrates our discussion topic: New gTLD applications and launches, and the latest from ICANN's draft applicants guidebook.

Final Thoughts: Next Steps for gTLD Applications

The Draft AGB shows that the program is becoming more organized, with a strong focus on transparency, supporting applicants, and involving the community. Although applying is still complex and costly, the new structure hopes to make the process clearer and easier to follow. For brands, communities, and innovators wanting to create their own digital identity at the top level, early planning and expert help will be essential. This round is likely to be the most competitive and most structured so far.

Ready to Participate? Let EBRAND Guide You Through

If your organization is considering applying for a new gTLD in the upcoming round, now is the time to start preparing. At EBRAND, we provide end-to-end strategic support – from feasibility assessments and application drafting to evaluation guidance and post-delegation services.

We have extensive experience supporting multiple success stories during the 2012 gTLD applications round, and we’re happy to share the insider knowledge and practical insights we’ve gained over more than a decade in this space. Get in touch with us to explore how we can help you successfully secure and operate your own top-level domain.

The post gTLD Applications: Unpacking ICANN’s Draft Applicant Guidebook appeared first on EBRAND.

]]>
Understanding Domain Names vs. Trademarks https://ebrand.com/blog/understanding-domain-names-vs-tradmarks/ Thu, 19 Jun 2025 08:58:48 +0000 https://ebrand.com/?p=49669 Every business needs domain names and trademarks to compete online. Whether you’re an SME breaking into new markets, or global enterprise launching a new products, these assets ensure you reach the right audience. But how your assets interact, when it comes to domain names vs. trademarks? What strategies help us get the most out of […]

The post Understanding Domain Names vs. Trademarks appeared first on EBRAND.

]]>
Every business needs domain names and trademarks to compete online. Whether you’re an SME breaking into new markets, or global enterprise launching a new products, these assets ensure you reach the right audience. But how your assets interact, when it comes to domain names vs. trademarks? What strategies help us get the most out of our assets, to secure our investments and protect our customers? 

This image of an unkempt garden illustrates our discussion topic: domain names vs. trademarks

This guide delves into the topics of domain names vs. trademarks, covering risks, rewards, and best practices for establishing a strong online presence. Whether you’re launching a new product, branching out into a new region, managing mergers and acquisitions, or rebuilding from scratch, understanding the relationship between domain names and trademarks makes a big difference. 

The Critical Differences Between Domains and Trademarks

Domain names and trademarks serve distinct purposes, though they often overlap. A domain name functions as a digital address, directing users to a specific website. As you know, domains mostly operate on a first-come, first-served basis, when it comes to ownership and expansion. While domains embody your online presence at large, trademarks protect brand identifiers (words, logos, or slogans) that distinguish goods and services in the marketplace. 

Crucially, registering a domain does not guarantee your trademark rights. The domain registration and trademark protection processes operate completely separately, with trademarks run by national IP offices, and domains run by registries and registrars. 

When it comes to domain registration, Corporate Domain Management services help audit and maintain domain portfolios, ensuring your digital alignment with your brand strategy. The interplay between domains and trademarks becomes critical when launching new products or entering new markets, where pre-emptive registrations and legal safeguards prevent conflicts. 

Do You Need a Trademark to Register a Domain?

No, a trademark is not required to register a domain (in most cases, safe a few select TLDs). Anyone can purchase an available domain name without legal proof of ownership over the matching brand term. For example, a startup can secure “websiteproduct.com” before trademarking “website product.” However, if another company already holds a trademark for that name, the new domain owner risks legal disputes. 

Some businesses adopt a reverse branding strategy, selecting a brand name based on available domains rather than vice versa. Companies like Reddit and Flickr chose their names after securing matching domains. While this approach offers flexibility, businesses must still conduct trademark searches to avoid future conflicts. 

Does a Trademark Keep You Safe from Cybersquatting and Impersonation?

A registered trademark does not automatically shield a brand from cybersquatting—where bad-faith actors register domains matching trademarks to exploit or extort the rightful owners. Scammers monitor trademark databases, snapping up domains as soon as new marks are applied for. 

This image of a man gardening illustrates our discussion topic: domain names vs. trademarks

Defensive registration strategies, such as securing common variations (e.g., “product-website.com” or “websiteproduct.net”), reduce risks. Domain blocking services and proactive monitoring further deter impersonation. Without these measures, businesses may face costly buybacks or legal battles to reclaim their digital identity. 

This legal complexity highlights why businesses must secure both domains and trademarks proactively. A startup might claim a domain before filing for trademark registration, but if another company already holds rights to the name, the domain owner could face litigation. Similarly, a trademark holder who neglects defensive domain registrations may find their brand exploited on imitation sites. The solution lies in treating domain strategy as an extension of intellectual property protection, ensuring web addresses align with legally protected trademarks before market entry. 

Trademark infringement in the domain space poses a growing threat, with bad-faith actors routinely registering domains that mimic established brands. Cybersquatters monitor trademark databases, grabbing domains the moment a new mark appears, then demanding high buyback fees. While a registered trademark provides legal leverage, it cannot automatically stop such abuses. Companies need monitoring tools to detect identical or confusingly similar domains. Ultimately, they may also need deploy enforcement tactics like cease-and-desist letters or the Uniform Domain Name Dispute Resolution Policy (UDRP)

Legal action works best when the infringing domain connects to competing goods or services, causing consumer confusion or reputational harm. However, not all cases are straightforward. Generic terms or geographic names may be harder to reclaim, as courts often favor registrants with legitimate uses. For example, a business running AppleGifts.com might avoid liability if it sells fruit baskets rather than tech products. These nuances underscore why companies should consult intellectual property attorneys to assess risks before pursuing litigation. 

Proactive Strategies for Brand Protection

Businesses should adopt a dual strategy, securing key domains early before filing for trademark registration in relevant jurisdictions. Defensive registrations, such as purchasing common misspellings, country-code TLDs like .de or .cn, and industry-specific extensions like .tech or .app, reduce impersonation risks. Corporate domain management services can audit portfolios for gaps, ensuring alignment with trademark holdings. 

Sophisticated monitoring complements a modern domain strategy, by covering the fast field of typo domains and variations across the thousands of TLDs that are available – and should extend beyond domains to social media, app stores, and marketplace listings, where counterfeiters often misuse brand assets. In cases of clear infringement, takedowns can mitigate misuse, while legal remedies like UDRP filings or lawsuits can recover domains, but especially concerning domain recovery, prevention always costs less than reaction. 

This image of two people smiling at a computer desk in the garden illustrates our discussion topic: domain names vs. trademarks

Conclusions: Top Tips for Domain Names vs. Trademarks

The interplay between domain names and trademarks demands proactive management to prevent costly The interplay between domain names and trademarks demands proactive management to prevent costly disputes and protect brand integrity. While these assets operate under separate systems, their strategic alignment forms the foundation of a secure digital presence. Companies that integrate domain strategy with its approach on Intellectual property and trademarks reduce risks, maintain consumer trust, and avoid legal pitfalls. 

To build this comprehensive protection, focus on four critical actions: 

  1. Align domains and trademarks early. Secure matching web addresses before launching a brand to avoid conflicts. 
  1. Monitor aggressively. Use automated tools to detect typosquatting, impersonation, and unauthorized use. 
  1. Enforce rights decisively. Pursue takedowns or escalate via UDRP actions or litigation against bad-faith registrants. 
  1. Think globally. Register trademarks and domains in all operational markets, including emerging regions. 

This dual approach of legal protection and digital vigilance creates multiple layers of defence against brand abuse. By implementing these practices consistently, businesses can navigate the complexities of online brand management while focusing on growth and innovation. For organizations seeking to evaluate their current position, a free professional brand audit identifies vulnerabilities and delivers tailored solutions. 

The post Understanding Domain Names vs. Trademarks appeared first on EBRAND.

]]>
HTTP vs HTTPS Redirects: Why Your Website Needs an Upgrade https://ebrand.com/blog/http-vs-https-redirects-why-your-website-needs-an-upgrade/ Thu, 12 Jun 2025 11:00:43 +0000 https://ebrand.com/?p=49606 Picture a customer entering their payment details on your website. Their credit card number, name, and address travel across the internet in plain text, just waiting for a hacker to reach out and take it. Without HTTPS, cybercriminals monitoring the connection captures this sensitive data with ease. Days later, fraudulent charges appear on the customer’s […]

The post HTTP vs HTTPS Redirects: Why Your Website Needs an Upgrade appeared first on EBRAND.

]]>
Picture a customer entering their payment details on your website. Their credit card number, name, and address travel across the internet in plain text, just waiting for a hacker to reach out and take it. Without HTTPS, cybercriminals monitoring the connection captures this sensitive data with ease. Days later, fraudulent charges appear on the customer’s statement, your company’s reputation suffers, and legal repercussions follow. This scenario happens every day to businesses that fail to implement HTTPS redirects.

This image of a security light illustrates our discussion topic: The differences between HTTP and HTTPS redirects for your website security, performance, and SEO.

Here, we’ll explore the differences between HTTP and HTTPS, and the best ways to establish a secure connection across your website. We’ll ultimately define why HTTPS redirects matter, how they protect your business, and the steps to implement them correctly.

HTTP: The Unsecured Foundation of Web Traffic

HTTP, or Hypertext Transfer Protocol, has facilitated web communication since the early 1990s. The protocol governs the ways that a web browser requests dat,a and how servers deliver web pages, images, and content. A HTTP connection work efficiently, but lacks security measures, transmitting all information in plain text. Hackers intercepting these communications can read everything—login credentials, personal details, and financial data.

Despite its widespread use, HTTP no longer meets modern security standards. Scammers exploit vulnerabilities in HTTP for malicious interception and data transfer. Major browsers now flag HTTP sites as “not secure,” and search engines penalize them in rankings. Companies still relying on HTTP risk losing customer trust, facing data breaches, and suffering SEO setbacks. In short, we must transition to a HTTPS connection, to secure data and stop scammers in their tracks.

HTTP vs HTTPS

Encrypted HTTPS solves HTTP’s security flaws by encrypting all data exchanges between browsers and servers. The “S” stands for secure, indicating the use of TLS (Transport Layer Security) or its predecessor, SSL (also known as Secure Sockets Layer). These security protocols scramble data so only the intended recipient can decode it, preventing hackers from reading intercepted traffic.

Beyond encryption, HTTPS authenticates websites, verifying their legitimacy through SSL certificates issued by trusted authorities. Hypertext transfer protocol secure means just that, ensuring trust and data integrity across your website. This authentication blocks phishing attempts and man-in-the-middle attacks, ensuring users connect to the real site rather than an imposter. Modern browsers display a padlock icon for HTTPS sites, signaling safety to visitors. Search engines also prioritize HTTPS websites, boosting their rankings over unsecured alternatives.

HTTPS Redirects: Enforcing Security Across Your Domain

When you switch to HTTPS from HTTP, proper redirects ensure all traffic uses the most secure protocol. Without them, visitors accessing old HTTP links may encounter errors, security warnings, or broken pages. HTTPS redirects automatically forward users from insecure URLs to their encrypted counterparts, preserving functionality and security.

This image of a key in a lock illustrates our discussion topic: The differences between HTTP and HTTPS redirects for your website security, performance, and SEO.

The most common redirects include permanent (301) and temporary (302) forwards. A 301 redirect tells search engines that a page has permanently moved, transferring SEO value to the new HTTPS address. A 302 redirect suits temporary changes, such as promotional campaigns, without affecting long-term rankings. Implementing these correctly prevents duplicate content issues and reinforces search visibility, while maintaining an encrypted connection across your pages.

The Benefits of HTTPS Redirects for Your Business

HTTPS redirects do more than fix a broken link or URL. Ultimately, the service enhances security, improves user trust, and strengthens SEO. Customers hesitate to submit sensitive information on unsecured sites, and browsers now warn them before loading HTTP pages. By enforcing HTTPS across all URLs, businesses eliminate these warnings, creating a seamless and trustworthy browsing experience.

Search engines favor HTTPS websites, ranking them higher in results. Google explicitly states that HTTPS works as a ranking signal, meaning secure sites gain a competitive edge. Proper redirects ensure that backlinks pointing to old HTTP URLs still pass authority to the new secure versions, preserving hard-earned SEO value.

Security compliance also plays a role. Industries handling sensitive data, such as finance and healthcare, must adhere to strict regulations to implement their infrastructure securely. HTTPS redirects help meet these requirements by ensuring all connections remain encrypted, reducing legal and financial risks.

How to Implement HTTPS Redirects Correctly

Setting up HTTPS redirects requires careful execution to avoid disruptions. The first step involves obtaining an SSL certificate from a trusted provider. Working with domain management experts ensures that this technical and multi-stage process stays smooth and secure, leaving your team to focus on their own business priorities.

This image of a technical specialist observing a watch through a specialised lens illustrates our discussion topic: The differences between HTTP and HTTPS redirects for your website security, performance, and SEO.

HTTPS redirects also work best alongside other domain management and domain security solutions. For businesses managing multiple domains, DNS services like Anycast enhance performance and reliability. Anycast routes traffic through the nearest web server location, reducing latency while maintaining HTTPS security. Combining HTTPS redirects with robust DNS infrastructure creates a fast, secure, and scalable web presence.

Final Thoughts: Secure Your Site Today

The internet no longer tolerates unsecured connections. HTTPS redirects protect user data, strengthen SEO, and build customer confidence. Companies delaying this upgrade risk losing traffic, facing security breaches, and falling behind competitors.

If you’re unsure whether your website enforces HTTPS correctly, our free HTTPS audit identifies vulnerabilities and provides actionable fixes. Don’t wait for a security incident—upgrade your redirects today and safeguard your business.

Get Your Free HTTPS Audit Now

The post HTTP vs HTTPS Redirects: Why Your Website Needs an Upgrade appeared first on EBRAND.

]]>
How to Secure Your Company’s Growing Domain Portfolio  https://ebrand.com/blog/how-to-secure-your-companys-growing-domain-portfolio/ Tue, 13 May 2025 14:23:05 +0000 https://ebrand.com/?p=48775 Modern businesses grow like trees—expanding into new markets, launching new products, and building layers of digital infrastructure over time. Each ring in the trunk represents another phase of growth, another branch in your organization’s ecosystem. But just as a tree must be strong enough to bear fruit, your digital presence must be robust enough to […]

The post How to Secure Your Company’s Growing Domain Portfolio  appeared first on EBRAND.

]]>
Modern businesses grow like trees—expanding into new markets, launching new products, and building layers of digital infrastructure over time. Each ring in the trunk represents another phase of growth, another branch in your organization’s ecosystem. But just as a tree must be strong enough to bear fruit, your digital presence must be robust enough to support your company’s expansion. That means securing every domain in your portfolio, ensuring they remain protected, optimized, and aligned with your business goals. 

This image of a tree in a field highlights the importance of  domain portfolio management for growing businesses.

Here, we’ll deliver all the tips you need for a strong, sustainable, and secure domain portfolio. As Forbes recently highlighted, 28% of all business is conducted online, meaning your domains support revenue, lead generation, and customer trust. Without auditing your portfolio, you invite risk—downtime, breaches, and reputational damage. Let’s dive into proactive domain monitoring, exploring the top industry tips to keep your portfolio safe. 

What Is Domain Portfolio Monitoring? 

Domain portfolio monitoring means implementing continuous oversight on all your registered domains, subdomains, and DNS configurations. This strategy helps detect any vulnerabilities, unauthorized changes, or malicious activity. Without monitoring your portfolio, you run into risks like domain hijacking, phishing scams, and costly downtime. Proactive monitoring reduces expenses, as fixing a breach after the fact costs far more than preventing one in the first place. 

Customers expect seamless, secure interactions with your brand. If a spoofed domain tricks them into entering sensitive data, their trust instantly erodes. Monitoring your portfolio ensures that you stay compliant with cybersecurity regulations, while safeguarding your website visitors. The alternative? Regulatory fines, lost revenue, and reputational damage. The stakes are too high to ignore. 

Securing Your Portfolio with EASM: External Attack Surface Management  

CISOs must look beyond their own domains for incoming threats. According to Statista38% of cybersecurity leaders see malware as a top 2025 risk, followed by email fraud (29%) and DDoS attacks. Cybercriminals often impersonate brands with lookalike domains to distribute malware or steal credentials. 

This is a graph of digital attack vector's in a client's domain portfolio, as part of an External Attack Surface Management (EASM) deployment on our X-RAY Digital Risk Protection Platform.

Domain monitoring identifies suspicious registrations mimicking your brand, allowing you to take them down before they cause harm. It also strengthens defenses against DDoS attacks by flagging unusual traffic patterns. By integrating EASM with portfolio monitoring, you secure not just your assets but your entire digital perimeter. 

Configuring Domains Properly: SPD, DMARC, and HTTPS 

A misconfigured domain is an open door for attackers. SPF, DKIM, and DMARC prevent email spoofing, ensuring only authorized servers send messages from your domain. Without them, phishing scams slip into inboxes, damaging credibility. DNS services ensure that you implement the technical tactics that your organization’s infrastructure needs to stay streamlined and scam-proof.

This image of a gardener highlights the importance of  domain portfolio management for growing businesses.

HTTPS redirects prove equally critical for modern businesses, supporting security, SEO, and valuable user experiences on your webpages. If a visitor lands on an unsecured HTTP version of your site, the lack of security exposes their data to malicious interception. Proper SSL enforcement and redirects eliminate this risk while boosting SEO, as Google prioritizes secure and trustworthy sites. 

Best Practices for Monitoring Your Website Assets

A well-secured domain portfolio requires more than just registering names—it demands proactive oversight of every digital asset tied to your brand. Neglecting subdomains, branding consistency, or renewal deadlines exposes your business to fraud, reputational damage, and operational disruption. Here’s how to lock down critical vulnerabilities:

1. Track Subdomains and Uncommon TLDs 

Subdomains (e.g., shop.yourbrand.comsupport.yourbrand.com) act as extensions of your primary domain, often hosting microsites, APIs, or regional services. Because they inherit your root domain’s authority, attackers target them for hijacking. Unmonitored subdomains can be weaponized for phishing, malware distribution, or credential theft—as seen in the SubDoMailing scam, where threat actors exploited over 8,000 abandoned subdomains belonging to major brands like eBay, McAfee, and CBS.

Attackers repurposed these dormant subdomains to blast fraudulent emails, bypassing spam filters and hitting countless consumers, as the Global Anti-Scam Alliance recently explored. To combat the kinds of threats, monitoring tools scan for unauthorized changes, orphaned subdomains, and suspicious activity, ensuring nothing slips through the cracks.

2. Enforce Consistent Branding

Every domain in your portfolio should reflect your brand’s identity. Inconsistent logos, outdated copy, or broken templates confuse customers and dilute trust. Regular audits ensure uniformity across all digital touchpoints. 

This image of a firefighter standing guard over a forest highlights the importance of  domain portfolio management for growing businesses.

3. Never Miss Registrations and Renewal Deadlines

No one owns a domain forever. Domains retain limited expiry dates, and everyone must stay up to date and on top of their expiries, event Google. In 2015, Google lost google.com when the domain renewed and someone bought it for only $12. Unlike physical assets, domains have no grace period for expiration. Once gone, recovery is costly, or impossible.

Relying on manual renewals is a gamble. Instead, implement renewal management services with clear stakeholders, SLAs, and multi-person approval chains. This eliminates single points of failure and ensures continuity, even during team turnover or oversight.

Conclusions: Secure Your Portfolio Before It’s Too Late 

Your domain portfolio is the backbone of your digital presence—yet gaps in monitoring leave you vulnerable to scams, breaches, and lost revenue. A full domain portfolio solution identifies risks, optimizes configurations, and ensures compliance with new and emerging regulations.

See what you’ve missed. Get a free domain audit today and secure your online assets now.

The post How to Secure Your Company’s Growing Domain Portfolio  appeared first on EBRAND.

]]>
DNS: How to Improve Your Company’s Infrastructure https://ebrand.com/blog/dns-how-to-improve-your-companys-infrastructure/ Fri, 02 May 2025 09:21:39 +0000 https://ebrand.com/?p=48442 Many businesses still treat DNS as a checkbox — until performance issues, downtime, or hidden costs start piling up. Some providers continue to charge per zone, restrict technical capabilities, or offer minimal security features. That setup might work for basic needs — but it doesn’t meet the demands of enterprise-grade infrastructure. Meanwhile, 81% of businesses […]

The post DNS: How to Improve Your Company’s Infrastructure appeared first on EBRAND.

]]>
Many businesses still treat DNS as a checkbox — until performance issues, downtime, or hidden costs start piling up. Some providers continue to charge per zone, restrict technical capabilities, or offer minimal security features. That setup might work for basic needs — but it doesn’t meet the demands of enterprise-grade infrastructure.

This image of a "construction ahead" warning sign illustrates our discussion topic: Exploring the best ways to build stable, secure, forward-thinking DNS infrastructure.

Meanwhile, 81% of businesses suffered Domain Name System attacks in the last five years, revealing just how exposed outdated systems have become. In this guide, we’ll share expert advice to help you manage and improve your organization’s DNS infrastructure — from foundational tips to the latest innovations shaping modern DNS strategy. 

The Importance of DNS for Modern Businesses 

DNS does more than route your traffic. Without DNS, most if not all of your digital communication breaks down including your email, your online shop, and your website. This crucial infrastructure enables users to reach your services, while protecting your brand from impersonation, and helping you scale across markets.

A strong DNS setup also reinforces security by defending against hijacking, phishing, and spoofing — all while helping your brand maintain trust and availability along every step of the way. 

The Risks of a Weak DNS 

When teams treat DNS as a low-priority task, problems accumulate. Human error, disorganized hosting, poor documentation, and security shortcuts all weaken your defenses. Many companies still manage DNS across silos or legacy systems, with permissions registered to employees who don’t even work at the company anymore. These kinds of blind spot and inefficiencies create high-value targets for attackers, if an unintentional glitch or outage doesn’t strike first. In 2024, researchers reported over one million domains potentially vulnerable to “Sitting Duck” DNS attacks — a threat that hijacks misconfigured domains to spread malware, run phishing campaigns, or impersonate trusted businesses.

The attack existed since 2018, but weak DNS practices keep it alive and effective, as we explore here. Clearly, well-protected and forward-thinking businesses take proactive steps to optimize and upgrade their DNS. 

Make Your Next DNS Improvements Hassle-Free

Domain Name Servers shouldn’t be a headache to manage — especially at scale. The right technical tools should give your team flexibility without adding complexity or risk. Look for a provider that supports a full range of DNS records and advanced configuration options — not just the basics. 

This image of two cranes crossing over in construction illustrates our discussion topic: Exploring the best ways to build stable, secure, forward-thinking DNS infrastructure.

DNSSEC (Domain Name System Security Extensions) adds a layer of authentication to prevent forged or manipulated DNS data, protecting users from redirection attacks. APEX Alias allows you to redirect traffic from the root of your domain to cloud services or CDN endpoints without compromising performance or compatibility. HTTPS forwarding helps enforce secure connections by automatically redirecting users from HTTP to HTTPS, supporting best practices in web security and compliance. 

When you have the right infrastructure in place, your team can avoid the frustration of fragmented setups — and manage DNS with confidence and control. 

Build Resilience and Speed with Global DNS 

As another tip, building a resilient, global DNS supports your organization’s security and growth. As you expand across regions, customer expectations for speed, uptime, and reliability grow with you. Your DNS needs to keep pace — and Anycast technology offers a major step forward. 

Anycast DNS improves performance and redundancy by routing each DNS query to the closest available server in a global network. This reduces latency, balances traffic, and helps maintain uptime — even during regional outages or high loads. Geo IP routing further enhances this setup by directing users to the most geographically relevant server based on their location, delivering a faster, more localized experience and improving global site performance. 

For high-risk or high-traffic environments, dedicated Anycast takes resilience a step further by placing your domain on its own isolated infrastructure. That means: 

  • Isolation and security from DDoS attacks 
  • Technical customization 
  • Premium positioning 
  • Risk management tools 

When reliability is absolutely critical, Dual Anycast adds another layer of protection. It runs two independent Anycast networks in parallel, ensuring uninterrupted service even if one network fails. This premium solution is especially well-suited to key assets like mail servers, ecommerce platforms, and login portals — where downtime simply isn’t an option. 

With the right combination of Anycast architecture and Geo IP routing, your DNS infrastructure delivers faster speeds, stronger uptime, and better resilience — all while giving you greater control of your global traffic. 

Stay in Control with Smart Admin Tools

Beyond the basics, modern DNS infrastructure should come with smart admin tools that help you stay agile, reduce risk, and recover quickly. Domain Name Systems can be highly technical, but the right management platform turns complexity into control — without adding unnecessary overhead. These features not only streamline your day-to-day operations but also prepare your infrastructure for long-term growth and resilience.

One essential feature is zone rollback, which lets you instantly revert to a previous configuration if a change causes issues — a simple way to undo mistakes without downtime.

Besides rollback, BIND import/export supports versatile, flexible, and well-run DNS infrastructure. The acronym refers to compatibility with the Berkeley Internet Name Domain (BIND) format, a widely used DNS configuration system. With BIND support, you can migrate zones or back up configurations easily, even across different platforms.

REST APIs give your developers and IT teams the ability to automate DNS changes and integrate DNS tasks into existing workflows or systems, saving time and reducing the chances of human error.

IP block restrictions add another layer of control by limiting access to your DNS management interface based on IP addresses. This prevents unauthorized users or regions from interacting with sensitive systems.

This image of an army of cranes building new high-rises illustrates our discussion topic: Exploring the best ways to build stable, secure, forward-thinking DNS infrastructure.

Single Sign-On (SSO) support improves security and usability by enabling staff to log in through trusted identity providers, reducing password fatigue and centralizing authentication across teams.

Time-based session validation (TSV) strengthens login security by enforcing session timeouts and re-authentication rules — a safeguard that minimizes exposure if credentials are compromised.

When something goes wrong — whether it’s a misconfiguration, a bad deployment, or an external issue — these tools let you act fast, maintain uptime, and keep your Domain Name System infrastructure secure and responsive.

Monitor Your Portfolio for Emerging Threats 

Improving your DNS infrastructure doesn’t stop at uptime. You also need to monitor your entire portfolio, including subdomains, to detect risks like impersonation or phishing. With visibility into DNS activity, you can spot suspicious changes early, stop copycat domains, and take proactive steps to protect users and brand reputation.

Finding a solution that bridges the worlds of Corporate Domain Management and Digital Risk Protection helps your online presence stay streamlined and secure. 

Conclusions: Strengthen Your DNS with Expert Support 

Working with the right partner helps you implement these improvements and create DNS infrastructure that’s ready for the future. The right provider delivers sophisticated tools, ISO-certified practices, 99.999% SLAs, and fair, scalable pricing.

If you want a Domain Name System that supports growth, stops attackers, and gives your team confidence — get in touch with our experts today. 

The post DNS: How to Improve Your Company’s Infrastructure appeared first on EBRAND.

]]>