Sorry if this question sounds weird but I would like to learn about this more and searching this on google gives me results about other keywords after coming to the word about. I think that's how Google is designed to work, so it gives me no information about https://about.
What is this domain about.*? Examples:
https://about.me
https://about.google
I understand that I can have about.mydomain.com but how come the above 2 domains do not have any extension at the end?
Is it possible for a normal user like us to have https://about.myname? i.e. https://about.kelsey?
TLDs are set up by ICANN, which, after approval, designates a registry that can assign domains under that TLD. So if you're influential enough to get ICANN to approve .kelsey, you're good to go; Google managed to do exactly that, hence the about.google URL. In many other cases, people use TLDs that have been assigned for a particular country as if they were generic (i.e., non-country-based) TLDs simply because they coincidentally look like one. .me, for instance, is the country TLD for the European country of Montenegro, it was originally not designed to have anything to do with the English pronoun "me". Similarly, TV stations like to use the TLD .tv, which was assigned to the Pacific island nation of Tuvalu. And that country specifically markets its domain names to TV stations.
Related
I have read that some of the first TLD where registered back in 90s, including .cz, .pl and other. So domain .SU was. That was domains for national needs.
But who have rights to become a maintainer of national domain? How that procedure looks like?
I also read that .SU TLD was proposed by Finnish student. But how can a student register national domain that supposed represent country?
I couldn't find information about that on Google.
You can find all data on the IANA webpage at https://www.iana.org/domains/root/db or just query it with whois.
.CZ is listed as created on 1993-01-12 and .PL on 1990-07-30
You can go back with some in 1985 like .UK or .US.
.SU had a complicated life because, as a ccTLD it should not exist anymore as the country it represented does not exist anymore. However for non technical reason, it subsists. You can find some discussions there : https://www.icann.org/news/announcement-2-2006-12-05-en
But who have rights to become a maintainer of national domain?
This is a complicated question, and not a technical one nor a programming one.
In short, IANA uses the ISO list on country codes (with some exceptions, like .UK and .EU) and takes input from the relevant government. Now the problem is that some countries are not stable, and also change. So there are a lot of complicated cases. Some ccTLDs are also marketed as non ccTLDs (like .CO or .TV) because the government decided to give its management to some external companies, for some financial agreement.
"Mistakes" happen also, see for example https://medium.com/#Oskar456/stolen-sk-domain-717e070f6735
You can find more about the IANA process at https://www.iana.org/help/cctld-delegation
Each IANA decision to delegate a ccTLD to a country is associated with a "IANA report" listing the justifications. You can read them for whatever country you wish at https://www.iana.org/reports, like a recent one for .TD for example at https://www.iana.org/reports/2018/td-report-20180227.html
The core business is codified, before ICANN even existed in https://www.rfc-editor.org/rfc/rfc1591
IANA adheres to that, and you can find further documentation at https://www.iana.org/domains/root/help
For more details in general, I would recommend you to read my extensive reply to a related question about TLDs and wars: https://superuser.com/questions/1332236/what-happens-to-country-specific-tlds-in-a-war-involving-that-country/1332238#1332238
As mention in title, I would like to know if the top level domain can be exactly 2 character and it is not country code.
Technically? Of course. Are there any? Well, if you're picky there's at least one that used to be a country code but no longer is (.SU). Will you ever be able to register a top-level domain that is not a country code? Almost certainly not.
I have a column which is made up of addresses as show below.
Address
1 Reid Street, Manchester, M1 2DF
12 Borough Road, London, E12,2FH
15 Jones Street, Newcastle, Tyne & Wear, NE1 3DN
etc .. etc....
I am wanting to split this into different columns to import into my SQL database. I have been trying to use Findstring to seperate by the comma but am having trouble when some addresses have more "sections" than others. ANy ideas whats the best way to go about this?
Many THanks
This is a requirements specification problem, not an implementation problem. The more you can afford to assume about the format of the addresses, the more detailed parsing you will be able to do; the other side of the same coin is that the less you will assume about the structure of the address, the fewer incorrect parses you will be blamed for.
It is crucial to determine whether you will only need to process UK postal emails, or whether worldwide addresses may occur.
Based on your examples, certain parts of the address seem to be always present, but please check this resource to determine whether they are really required in all UK email addresses.
If you find a match between the depth of parsing that you need, and the assumptions that you can safely make, you should be able to keep parsing by comma indexes (FINDSTRING); determine some components starting from the left, and some starting from the right of the string; and keep all that remains as an unparsed body.
It may also well happen that you will find that your current task is a mission impossible, especially in connection with international postal addresses. This is why most websites and other data collectors require the entry of postal address in an already parsed form by the user.
Excellent points raised by Hanika. Some of your parsing will depend on what your target destination looks like. As an ignorant yank, based on Hanika's link, I'd think your output would look something like
Addressee
Organisation
BuildingName
BuildingAddress
Locality
PostTown
Postcode
BasicsMet (boolean indicating whether minimum criteria for a good address has been met.)
In the US, just because an address could not be properly CASSed doesn't mean it couldn't be delivered - cip, my grandparent-in-laws live in enough small town that specifying their name and city is sufficient for delivery as local postal officials know who they are. For bulk mailings though, their address would not qualify for the bulk mailing rate and would default to first class mailing. I assume a similar scenario exists for UK mail
The general idea is for each row flowing through, you'll want to do your best to parse the data out into those buckets. The optimal solution for getting it "right" is to change the data entry method to validate and capture data into those discrete buckets. Since optimal never happens, it becomes your task to sort through the dross to find your gold.
Whilst you can write some fantastic expressions with FINDSTRING, I'd advise against it in this case as maintenance alone will drive you mad. Instead, add a Script Transformation and build your parsing logic in .NET (vb or c#). There will then be a cycle of running data through your transformation and having someone eyeball the results. If you find a new scenario, you go back and adjust your business rules. It's ugly, it's iterative and it's prone to producing results that a human wouldn't have.
Alternatives to rolling your address standardisation logic
buy it. Eventually your business needs outpace your ability to cope with constantly changing business rules. There are plenty of vendors out there but I'm only familiar with US based ones
upgrade to SQL Server 2012 to use DQS (Data Quality Services). You'll probably still need to buy a product to build out your knowledge base but you could offload the business rule making task to a domain expert ("Hey you, you make peanuts an hour. Make sure all the addresses coming out of this look like addresses" was how they covered this in the beginning of one of my jobs).
I'm writing a Regex to validate email. The only one thing confuse me is:
Is it possible to have single character for top level domain name? (e.g.: lockevn.c)
Background: I knew top level domain name can be from 2 characters to anything (.uk, .us to .canon, .museum). I read some documents but I can't figure out does it allow 1 character or not.
It is technically possible, however, there are no single character tlds that have been accepted into the root (as of the moment) so the answer is:
Yes, it is possible to have single character for top level domain name, however, there are currently no single character TLDs in the root.
You can see the list of TLDs that are currently in the root at this URL:
http://data.iana.org/TLD/tlds-alpha-by-domain.txt
RFC-952 shows what a "name" is, this includes what is valid as a top level domain:
A "name" (Net, Host, Gateway, or Domain name) is a text string up
to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus
sign (-), and period (.).
Additionally, the grammar from RFC-952 shows:
<name> ::= <let>[*[<let-or-digit-or-hyphen>]<let-or-digit>]
RFC-1123 section 2.1 specifically allowed single letter domains & subdomains, changing the initial grammar of RFC-952 from starting with just a letter to being more relaxed, so now you are allowed to have single letter top level domains that are a number:
2.1 Host Names and Numbers
The syntax of a legal Internet host name was specified in RFC-952.
One aspect of host name syntax is hereby changed: the
restriction on the first character is relaxed to allow either a
letter or a digit. Host software MUST support this more liberal
syntax.
EDIT: As per #mr.spuratic's comment, RFC-3696 section 2 tightened the rules for top level domains, stating:
There is an additional rule that essentially requires
that top-level domain names not be all-numeric.
This means that:
a. is a valid top level domain
1. is not a valid top level domain
A very unscientific test of this shows that if I add "a" into my hosts file pointing to my local machine, going to http://a in my address bar does show my Apache welcome page.
I'm not sure about the internet standard, but in practice, no.
See,
http://www.norid.no/domenenavnbaser/domreg.html
and,
http://sqa.fyicenter.com/Online_Test_Tools/Domain_Name_Format_Validator.php
You should DEFINITELY allow 1-character domains since some registries allow them not by accident (and I speak of quite big registries like UK, Germany, Poland, Ireland too - so important contributors to the Internet community, not oney exotic small exceptions). Since I also plan using such domains, that definitely work also with all e-mail services I used, letters AND numbers, I really would give the hint to allow this, else your script might need later correction.
Also some of the biggest internet companies use such domains - one of the most famous examples is Twitters t.co for shortening. Other companies I know of who have such domains are Facebook, Google, PayPal, Deutsche Telekom. But the list is longer and also some bigger investors hold them as assets.
By the way as proof there is a website trading this kind of domains online if You search for "1 letter domain names" :)
We've currently a debate here about original domain names versus generic domain names in term of seo efficiency.
We mean by generic domain names, domains like :
- buy-hifi.com
- game-news.com
- easy-meet.com
We mean by original domain names, domains like :
- hifihot.com
- gamesmaniac.com
- lovein.com
What is your opinion ? (actually it's more a poll than a actual question but developments are welcome)
I remember reading an article about AccuWeather being offered the chance to buy weather.com. They passed on it because it didn't reflect their image, The Weather Channel snatched it afterwards, and AccuWeather ended up regretting their decision. While a generic name won't sing your brand, and a brand is important, it's hard to say which is better. I couldn't imagine generic domain names for companies like Apple, Microsoft, IBM, etc., so I suppose it depends. What a lousy answer. How about this: both. Why not have both name types and offer redirection?